JBossWS and OSGi Container in EAP 5

Solution Verified - Updated -

Issue

I'm using custom code to deploy a JAX-WS endpoint via JBossWS Native in my custom OSGi container in EAP 5. When JBossWS tries to load the endpoint implementation at runtime, it fails with a ClassNotFoundException.

Resolution

Open a support case and ask to apply one off patch JBPAPP-11150. The support engineer will likely verify the scenario before providing the patch.

Root Cause

JBossWS is using the TCCL to load classes referenced in the endpoint interface, but it should be using the endpoint interface's classloader instead. This will never be a problem in a standard setup, but it manifests itself when a nonstandard classloading structure is used.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments