[jbossws-issues] [JBoss JIRA] (JBWS-3479) Implement @org.jboss.ws.api.annotation.WebContext support for POJO endpoints
[
https://issues.jboss.org/browse/JBWS-3479?page=com.atlassian.jira.plugin....
]
Alessio Soldano commented on JBWS-3479:
---------------------------------------
Hi Jim,
well, my point of view is that this would a) simplify the api from a user point of view
(you could use this annotation regardless of the type of ws endpoint, pojo or ejb3), b)
allow fully configuring pojo endpoints without web.xml, again something users might like.
The context-root, btw, is not set in the web.xml, but in the jboss-web.xml, which is still
not portable, so to me allowing using the @WebContext annotation here would not really
affect portability.
This said, I agree supporting this adds a bit of complexity when computing the actual
context-root, virtual-host etc., but I still believe it's worth exploring the
feasibility of this feature req issue.
Implement @org.jboss.ws.api.annotation.WebContext support for POJO
endpoints
----------------------------------------------------------------------------
Key: JBWS-3479
URL: https://issues.jboss.org/browse/JBWS-3479
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: jbossws-integration
Reporter: Richard Opalka
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira