[jbossws-issues] [JBoss JIRA] (JBWS-3453) JBossWSBusFactory check on Spring availability relies on TCCL only
[
https://issues.jboss.org/browse/JBWS-3453?page=com.atlassian.jira.plugin....
]
Steve Andrews commented on JBWS-3453:
-------------------------------------
On our project, we experienced this issue, but only intermittently. Is there something
about the nature of this issue that would cause it to only manifest after some period of
time? In other words, we have the requisite Spring classes in our WAR and calling a
remote web service via CXF works fine for awhile. At some point, we end up getting the
NoClassDefFoundError described in https://issues.jboss.org/browse/JBPAPP6-492
JBossWSBusFactory check on Spring availability relies on TCCL only
------------------------------------------------------------------
Key: JBWS-3453
URL: https://issues.jboss.org/browse/JBWS-3453
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-cxf
Reporter: Alessio Soldano
Assignee: Alessio Soldano
Fix For: jbossws-cxf-4.1.0.Beta1
JBossWSBusFactory has a check on Spring availability to decide the type of CXF BusFactory
to build (Spring or not). The check is on TCCL being able to load Spring classes, but
that's not enough in a JBoss Modules environment. As a matter of fact, that check
needs to be extended to the defining classloader of the JBossWSBusFactory (which is the
classloader for the org.jboss.ws.jaxws-client module), to be sure the factory can actually
be loaded (it's going to be loaded using the defining classloader and of course the
CXFBusFactory imports Spring classes)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira