[esb-issues] [JBoss JIRA] Closed: (JBESB-3257) WSDL unavailable for SOAPProxy + HTTPGateway on server restarts
David Ward (JIRA)
jira-events at lists.jboss.org
Fri Apr 16 12:32:26 EDT 2010
[ https://jira.jboss.org/jira/browse/JBESB-3257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Ward closed JBESB-3257.
-----------------------------
Resolution: Done
Work completed on JBESB_4_7_CP branch.
Committed revision 32590.
> WSDL unavailable for SOAPProxy + HTTPGateway on server restarts
> ---------------------------------------------------------------
>
> Key: JBESB-3257
> URL: https://jira.jboss.org/jira/browse/JBESB-3257
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Web Services
> Affects Versions: 4.7 CP1
> Reporter: David Ward
> Assignee: David Ward
> Fix For: 4.7 CP2
>
>
> 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/product/rosetta/src/org/jboss/soa/esb/listeners/config/mappers120/XMLBeansModel.java
> (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
More information about the esb-issues
mailing list