When the Spring integration is enabled, the TCCL that's set at the time the user endpoint methods are executed is an instance of DelegateClassLoader whose parent actually grants user visibility over classes he should only be given access if he declared a proper module dependency.
In addition, the DelegateClassLoader is not recognized by the remote EJB client subsystem. This causes remote EJB invocations from webservice implementations to fail with "EJBCLIENT000025: No EJB receivers available...".
I'm so sorry, but I just realized that the fix for JBWS-3858 (BZ1174922), which was expected to be in 4.3.4.Final is not there (at least if Astigmatismic eyes are not getting confused by the commits lines).
This means we need a new release, 4.3.5 (I assume) to ensure the fix goes to 6.3 and 6.4.x as scheduled.
I'll update the associate upgrade BZs to reflect that right away.
the fix for JBWS-3858 is there in 4.3.4.Final, see https://source.jboss.org/changelog/JBossWS?cs=19153 . So no need for a 4.3.5 for this issue.
Only presence of code changes related to this issue will be checked. Spring integration for JBossWS CXF is not supported on EAP 6.
Code changes included in 6.4.0.ER1
Alessio Soldano <firstname.lastname@example.org> updated the status of jira JBWS-3858 to Closed