[
https://jira.jboss.org/jira/browse/JBESB-3255?page=com.atlassian.jira.plu...
]
David Ward commented on JBESB-3255:
-----------------------------------
There is nothing in the log. The WSDL just silently does not show up on server re-starts
(again, it does on hot deploys and re-deploys). The CNFE is silently
"swallowed" because otherwise the continous integration builds break (as the
classpath is not set up correctly for those). I can see that at least a log.warn(...)
would be nice in the future at least, and probably spending the time fixing the junit
classpath.
The basic problem is that XMLBeansModel is in rosetta.jar, and SOAPProxy is in soap.esb,
and whereas soap.esb is available to the classloader of XMLBeansModel during hot deploys
and re-deploys, it doesn't seem to be for server re-starts. Otherwise,
SOAPProxy.class would be found.
WSDL unavailable for SOAPProxy + HTTPGateway on server restarts
---------------------------------------------------------------
Key: JBESB-3255
URL:
https://jira.jboss.org/jira/browse/JBESB-3255
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Web Services
Affects Versions: 4.7
Reporter: David Ward
Assignee: David Ward
Fix For: 4.8
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:
http://anonsvn.jboss.org/repos/labs/labs/jbossesb/branches/JBESB_4_7_CP/p...
(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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira