Community
Participate
Working Groups
Build ID: I20070313-1051 Steps To Reproduce: 1) Create EJB 3.0. When expand the project has no “Deployment Descriptor” node 2) Create ejb-jar.xml with contents: <?xml version="1.0" encoding="UTF-8"?> <ejb-jar xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd" id="ejb-jar_ID" version="3.0" > </ejb-jar> 3) Close and open the J2EE perspective. 4) The EJB 3.0 project has Deployment Descriptor 1.4.
Neeraj- this looks like a Navigator View problem. (I believe he means the EJB's Deployment Descriptor node shows 2.1 instead of 3.0.)
I want to generalize the bug, because it appears for all types of Java EE 5 projects. Steps to reproduce for EAR 5: 1) Create EAR 5. When expand the project has no “Deployment Descriptor” node 2) Create EarContent/META-INF/application.xml file. 3) Add this content to the xml file: <?xml version="1.0" encoding="UTF-8"?> <application version="5" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd "> </application> 4) "Deployment Descriptor 1.4" node appears. Steps to reproduce for EJB 3.0: 1) Create EJB 3.0. When expand the project has no “Deployment Descriptor” node 2) Create ejbModule/META-INF/ejb-jar.xml file. 3) Add this content to the xml file: <?xml version="1.0" encoding="UTF-8"?> <ejb-jar xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://java.sun.com/xml/ns/javaee" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd" id="ejb-jar_ID" version="3.0" > </ejb-jar> 4) "Deployment Descriptor 2.1" node appears. Steps to reproduce for Web 2.5: 1) Create Web 2.5. When expand the project has no “Deployment Descriptor” node 2) Create WebContent/WEB-INF/web.xml file. 3) Add this content to the xml file: <?xml version="1.0" encoding="UTF-8"?> <web-app id="WebApp_ID" version="2.5" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd"> <display-name>web25</display-name> <welcome-file-list> <welcome-file>index.html</welcome-file> <welcome-file>index.htm</welcome-file> <welcome-file>index.jsp</welcome-file> <welcome-file>default.html</welcome-file> <welcome-file>default.htm</welcome-file> <welcome-file>default.jsp</welcome-file> </welcome-file-list> </web-app> 4) "Deployment Descriptor 1.4" node appears. In all above cases, if the deployment descriptor does not appear, try close and reopen the J2EE perspective. We are quite deep in the problem and will have patch soon.
Created attachment 62208 [details] patch The proposed patch limits the deployment descriptor tree to appear to projects with version up to J2EE 1.4 specification. The trigger point for the navigator content does not include any more facet versions of Java EE 5 and later. The idea is that at the moment WTP provides deployment descriptor tree to project up to J2EE 1.4. For Java EE 5 (and later) projects the adopter will provide their own deployment descriptor tree, it they want one.
want to drop this tonight
dropped to build
Verified with the I200705022121 I-build.
closing
