Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 331000

Summary: Import of EJB3 EAR file for JBoss 5: "The selected runtime does not support the version of the archive."
Product: [WebTools] WTP Java EE Tools Reporter: Wolfgang Knauf <wolfgang.knauf>
Component: jst.j2eeAssignee: jst.j2ee <jst.j2ee-inbox>
Status: CLOSED FIXED QA Contact: Chuck Bridgham <cbridgha>
Severity: major    
Priority: P3 CC: jsholl
Version: unspecified   
Target Milestone: 3.2.3   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Wolfgang Knauf CLA 2010-11-24 04:21:32 EST 
Build Identifier: Eclipse M20100909-0800, wtp-R-3.2.2-20100915173744

I try to import the EAR file found at 
http://www.informatik.fh-wiesbaden.de/~knauf/KomponentenArchitekturen2008/stateless/Stateless.ear
into WTP 3.2.2 and a "JBoss 5" runtime.

This does not work, because the import wizard shows an error message "The selected runtime does not support the version of the archive.".

If I import it in a "None" runtime, it works and I see that the facets are JavaEE6. 

So the problem is that my sample EAR, which is a valid JavaEE5 project, is considered JavaEE6, and this version is rejected by the "JBoss 5" server definition.

I assume that if no specific JavaEE version can be detected through deployment descriptors, the import wizard should pick the max version supported by the server.
Other solution: add a "pick JavaEE version" combobox to the first page of the wizard (more control for the user ;-)).

Reproducible: Always
Comment 1 Jason Sholl CLA 2010-11-24 08:18:29 EST 
This has already been fixed in 3.2.3.  I confirmed that it is failing for me with 3.2.2, but is now working in the latest 3.2.3 declared build, I-3.3.0-20101118204151
Comment 2 Wolfgang Knauf CLA 2010-11-26 09:34:12 EST 
Yes, it works with wtp-M-3.2.3-20101118072507