Loading...

XML

Word

Printable

Type: Enhancement
Resolution: Done
Priority: Major
Fix Version/s: jbossws-cxf-5.2.4.Final
Affects Version/s: None
Component/s: jbossws-cxf, jbossws-integration
Labels:
None

Git Pull Request:
https://github.com/jbossws/jbossws-cxf/pull/81, https://github.com/jbossws/jbossws-cxf/pull/82

After ~~JBEAP-5527~~ , the TCCL is no 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.

is incorporated by

JBEAP-15236 [GSS](7.1.z) TCCL not set for JBoss WS deployment

Verified

relates to

JBWS-3986 Improve isolation between integration code and user code

Closed

Assignee:: Ivo Studensky

Reporter:: Brad Maxwell

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Created:: 2018/08/16 10:35 AM

Updated:: 2022/09/09 7:09 AM

Resolved:: 2018/08/27 5:55 AM

Details

Description

Attachments

Issue Links

Activity

People

Dates