Type: Feature Request
Status: Open (View Workflow)
Affects Version/s: None
Fix Version/s: None
Security Level: Public (Everyone can see)
Similar Issues:Show 10 results
JBWS-3276 Implement support for POJO endpoints with no web.xml in archive JBWS-2268 Implement @PostConstruct and @Predestroy annotations support for POJO based endpoints (JSR 109 conformance) JBWS-3343 Support for both EJB3 and POJO WS endpoints in war archives JBWS-1603 Implement pooling of JSE endpoints JBWS-865 Support security annotations for EJB3 endpoints JBWS-2410 Implement @PostConstruct and @Predestroy annotations support for POJO based endpoints (JSR 109 conformance) JBWS-87 Support for EJB endpoints JBWS-1107 Spaces around the class specified in servlet-class of the POJO endpoint causes ClassNotFound exception. JBWS-3441 Support CDI interceptors for POJO JAX-WS services JBWS-2634 Implement support for @EJB annotations in WS components
We support @WebContext on EJB endpoints now.
Since Servlet 3.0 spec allows web deployments
without web.xml it is worth to support this annotation
also on POJO WS endpoints.
There are however two restrictions that must be ensured.
If there are multiple WS endpoints in web archive
all annotated with @WebContext annotation then the following
restriction must apply:
- contextRoot value must be the same for all @WebContext annotated endpoints
- virtualHost value must be the same for all @WebContext annotated endpoints
- if there's provided jboss-web.xml or jboss-webservices.xml with context root in deployment
this DD driven context root will have higher priority than context root specified in annotations.