]
David Ward commented on JBESB-2822:
-----------------------------------
It has something to do with the new http-gateway. On trunk fronting a service with
soapproxy in it with http via *JBR* works fine, and again the old http-gateway worked fine
too.
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: