[jbossws-issues] [JBoss JIRA] (JBWS-4135) TCCL not set for JBoss WS deployment

[Brad Maxwell (JIRA)]

     [ https://issues.jboss.org/browse/JBWS-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brad Maxwell updated JBWS-4135:
-------------------------------
    Description: 
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.



  was:
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.





> TCCL not set for JBoss WS deployment
> ------------------------------------
>
>                 Key: JBWS-4135
>                 URL: https://issues.jboss.org/browse/JBWS-4135
>             Project: JBoss Web Services
>          Issue Type: Enhancement
>          Components: jbossws-cxf, jbossws-integration
>            Reporter: Brad Maxwell
>            Assignee: Alessio Soldano
>             Fix For: jbossws-cxf-5.2.4.Final
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)