-
Bug
-
Resolution: Done
-
Major
-
7.1.3.GA
-
None
After JBEAP-5527 , the TCCL is not longer set to the DelegateClassloader and is now null, which is causing issues with applications when the applications WS class is instantiated and initializes some variables that use the TCCL to look for implementations. Setting the TCCL to the deployment classloader would fix the issue and resolve the regression.
- incorporates
-
JBWS-4135 TCCL not set for JBoss WS deployment
- Resolved
- is caused by
-
JBEAP-5527 (7.0.z) Improve isolation between integration code and user code
- Verified
- is incorporated by
-
JBEAP-15300 [GSS](7.1.z) Upgrade to JBoss WS CXF to 5.1.11.Final
- Closed