[esb-issues] [JBoss JIRA] Commented: (JBESB-2822) SOAPProxy wsdl contract is not available using new http gateway
[
https://jira.jboss.org/jira/browse/JBESB-2822?page=com.atlassian.jira.plu...
]
Tom Fennelly commented on JBESB-2822:
-------------------------------------
Hmmm... looking at the SOAPProxyWsdlContractPublisher... it makes a http lookup to load
the wsdl. What will happen here when the ws endpoint is running in the same container?
If the .esb is being deployed before the web container is "open for business"
and accepting requests, won't this wsdl lookup fail or hang?
I did test some of these SOAPProxy quickstarts, but might have deployed and undeployed the
quickstarts to a running server i.e. where the webcontainer is fully deployed and
accepting requests.
SOAPProxy wsdl contract is not available using new http gateway
---------------------------------------------------------------
Key: JBESB-2822
URL: https://jira.jboss.org/jira/browse/JBESB-2822
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.7
Reporter: David Ward
Fix For: 4.7
When using thew new http-gateway fronting the SOAPProxy action, an HTTP wsdl contract
link is missing from the contracts web application. This used to work with the old
http-provider, and still works with the current jbr-provider.
I put debug into the contract.war/index.jsp, and noticed that when using the new
http-gateway, only 1 EPR (INVM) is being returned by registry.findEPRs(serviceCategory,
serviceName). When I instead use the jbr-provider, I get 2 EPRs (INVM + HTTP) as
expected.
FYI, the publisher (SOAPProxyWsdlContractPublisher) is an instance of ContractPublisher,
not ContractReferencePublisher, but this shouldn't matter.
--
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