Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 318483 - earArtifactEdit.getApplication().getVersion() returns null
Summary: earArtifactEdit.getApplication().getVersion() returns null
Status: RESOLVED WONTFIX
Alias: None
Product: WTP Java EE Tools
Classification: WebTools
Component: jst.j2ee (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: 3.4   Edit
Assignee: Roberto Sanchez Herrera CLA
QA Contact: Chuck Bridgham CLA
URL: \\cestorage\JS_QM\procedures_results\...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-30 11:09 EDT by Dimo Stoilov CLA
Modified: 2012-05-01 15:46 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dimo Stoilov CLA 2010-06-30 11:09:21 EDT
We have a EAR 1.3->1.4 migration procedure that 
1)converts the application.xml from 1.3 to 1.4 
2)changes the facet version from 1.3 -> to 1.4. 
The problem is after these changes org.eclipse.jst.j2ee.componentcore.util.EARArtifactEdit.getEARArtifactEditForRead(project).getApplication().getVersion() retruns null. Prior to Helios it returned 1.4.

For manual reproduction I assume the following steps has to be done:
1)Create an EAR 1.3 project - the DD node in the tree shows 1.3 version
2)change the appliication.xml - from 1.3 to 1.4 version - i.e replace: 

<!DOCTYPE application PUBLIC "-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN" "http://java.sun.com/dtd/application_1_3.dtd">
<application id="Application_ID">

with:

<application xmlns="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="1.4" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd">

3)In helios the DD node is still 1.3. 
Prior to Helios - the DD node becomes 1.4
Comment 1 Carl Anderson CLA 2010-09-23 14:02:25 EDT
Assigning to Jason for initial investigation.
Comment 2 Carl Anderson CLA 2011-04-28 12:12:01 EDT
Dimo, we cannot reproduce this.  Is this still a problem?  Could someone else with access to your migration procedure debug through this?
Comment 3 Carl Anderson CLA 2012-05-01 15:46:34 EDT
We're having a hard time replicating this- if you still see this issue, then
reopen this bug with more information.