Bug 194920 - No validation of uplevel DDs
Summary: No validation of uplevel DDs
Status: NEW
Alias: None
Product: WTP Java EE Tools
Classification: WebTools
Component: jst.j2ee (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: Future   Edit
Assignee: jst.j2ee CLA
QA Contact: Chuck Bridgham CLA
URL:
Whiteboard: JEE5
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2007-06-29 10:32 EDT by Tim deBoer CLA
Modified: 2008-05-22 14:45 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tim deBoer CLA 2007-06-29 10:32:05 EDT
If I create a J2EE 1.4 EAR and then upgrade the DD to EE5 (i.e. update the schema to EE5 and start adding some elements that didn't exist in 1.4) there is no error message to let me know that this is invalid in a J2EE 1.4 EAR. We should display an error because otherwise the user may assume that they can either run it on a J2EE 1.4 server (which would fail) or that they've successfully upgraded to an EE5 EAR (which they haven't since the facet hasn't changed, and WTP will block them from running on an EE5 server).

We should do two things:
1) Display a validation error whenever the user has an uplevel schema in an older EAR or module. (e.g. a 1.4 web DD in a 1.3 web module)

2) [Nice to have] Add a quick fix that will fix the schema to the 'correct' DD level.

3) [For bonus points] Add a quick fix that will update the facet to the correct level. For modules this could update the EAR as well, or just ensure that validation causes an error on the EAR if the module version is higher than the EAR.
Comment 1 Chuck Bridgham CLA 2008-05-22 14:38:03 EDT
Moving normal/lower severity defects to 301 for now
Comment 2 Carl Anderson CLA 2008-05-22 14:45:19 EDT
This is helpwanted - moving target to Future