-
Feature Request
-
Resolution: Done
-
Major
-
None
-
None
We need to avoid exposing ws stacks implementation classes (and all their dependencies) to the user classpath. This implies completely reviewing the classloading in both JBossWS-Native and JBossWS-CXF to make sure the proper classloader is used depending on the needs instead of generally going through the thread context classloader.
- is blocked by
-
JBWS-3224 Review the jbossws-spi ServiceLoader to allow for passing a classloader in
- Closed
- is related to
-
JBPAPP-7220 Cannot package spring-beans.jar in application that uses JBossWS-CXF
- Closed
- relates to
-
JBPAPP-8027 JBossWS uses JAXP in a non-modular classloading compatible way
- Closed
-
AS7-511 Upgrade to JBossWS-CXF 4.0.0.Alpha4
- Resolved