[
https://issues.jboss.org/browse/JBWS-3479?page=com.atlassian.jira.plugin....
]
Jim Ma commented on JBWS-3479:
------------------------------
I'd prefer to not support this. We introduce the @WebContext for the ejb ws endpoint,
partly because there is no descriptor in ejb archive to specify the contextRoot,
urlPattern, virtualHost etc. Given there is web.xml which can specify all these things in
@WebContext, we can ask user to configure in web.xml instead of annotation. It will be
more portable and less complex to check various above restriction. Your opinion ?
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
Fix For: jbossws-cxf-4.2
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