When hot-deploying or re-deploying an .esb archive with SOAPProxy + HTTPGateway, the WSDL shows up in the contract JSP application no problem. However, when re-starting the server (and leaving the .esb archive in deploy), the WSDL does NOT show up in the JSP.
This does NOT affect the service from working, as it still gets deployed and still functions. The problem is the missing WSDL.
The problem is in:
(as well as mappers 110 and 100).
In mappers120, line 608 is throwing a ClassNotFoundExeption, then falling into Line 610. The class it's looking for, of course, is "org.jboss.soa.esb.actions.soap.proxy.SOAPProxy".
The fix is probably simple: make sure the right thread context class loader is in effect.