Bugzilla – Full Text Bug Listing
| Summary: | J2EE Runtime Library doesn't support Dynamic Web Module 3.0 | ||
|---|---|---|---|
| Product: | [WebTools] WTP ServerTools | Reporter: | arjan tijms <arjan.tijms> |
| Component: | jst.server | Assignee: | jst.server <jst.server-inbox> |
| Status: | NEW --- | QA Contact: | Elson Yuen <eyuen7> |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
Build Identifier: 20110916-0149 When configuring the "J2EE Runtime Library" server runtime environment to point to either GlassFish 3.3.1 or JBoss AS 6.0, it seems that Dynamic Web Module 3.0 is not supported. When creating a new dynamic web project with the J2EE Runtime Library as Target runtime, the range of Dynamic web module versions that can be selected only ranges between 2.2 and 2.5. For existing 3.0 based projects, J2EE Runtime Library can not be selected as a Target runtime. When manually changing the version to 3.0 in /.settings/org.eclipse.wst.common.project.facet.core.xml for a project that uses the J2EE Runtime Library, the following message is displayed in the Markers views: Faceted Project Problem Project facet Dynamic Web Module 3.0 is not supported by target runtime J2EE Runtime Library. In both cases I validated the jars in the libraries contained valid Servlet 3.0 spec jars. For JBoss AS 6.0 this is [jboss home]/common/lib/jboss-servlet-api_3.0_spec.jar and for Glassfish this is [glassfish home]/glassfish/modules/javax.servlet.jar. The J2EE Runtime Library does seem to support other facets in version from Java EE 6, e.g. JPA 2.0 was selectable when adding the JPA facet. Reproducible: Always Steps to Reproduce: 1. Add new Server Runtime Environment 2. Choose Basic/J2EE Runtime Library 3. Enter location [glassfish home]/glassfish/modules or [jboss home]/common/lib 4. Create new Dynamic Web Project 5. Select "J2EE Runtime Library" for the Target runtime