[jbossws-issues] [JBoss JIRA] Issue Comment Edited: (JBWS-3223) Runtime ws client classloader setup on AS7
[
https://issues.jboss.org/browse/JBWS-3223?page=com.atlassian.jira.plugin....
]
Alessio Soldano edited comment on JBWS-3223 at 2/17/11 1:09 PM:
----------------------------------------------------------------
This is going to include:
- changes on the service loader mechanism of our JAXWS api libs (including automatic load
of jbossws-client module)
- changes on client entry points to both CXF and Native JAXWS stacks, so that the properly
TCCL is set (allowing for Apache CXF - for instance - to successfully detect it's own
components)
was (Author: alessio.soldano(a)jboss.com):
This is going to include:
- changes on the service loader mechanism of our JAXWS api libs (including automatic load
of jbossws-client module)
- changes on client entry point to both CXF and Native JAXWS stacks, so that the properly
TCCL is set (allowing for Apache CXF -for instance- to successfully detect it's own
components)
Runtime ws client classloader setup on AS7
------------------------------------------
Key: JBWS-3223
URL: https://issues.jboss.org/browse/JBWS-3223
Project: JBoss Web Services
Issue Type: Task
Security Level: Public(Everyone can see)
Components: jbossws-cxf, jbossws-integration, jbossws-native
Reporter: Alessio Soldano
Assignee: Alessio Soldano
Fix For: jbossws-native-4.0, jbossws-cxf-4.0
One of the design requirements around JBoss AS 7 is hiding implementation classes from
user classpath. However, we need to ensure users can use basic JAXWS functionalities (and
any other feature covered by JSR specs) from any servlet and ejb3. Basically, we need to
make sure client side WS functionalities are always available (whenever the WS subsystem
is on), while having the API (JAXWS, JWS, SAAJ, etc.) libs only available on user
classpath.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira