[jboss-dev-forums] [JBoss ESB Development] - Re: SOAPProxy+AS5: INVM contract unavailable w/classpath URI

[dward]

"Kevin.Conner at jboss.com" wrote : First, only when WSDL is exposed through the HTTP/JBR endpoints should the contract publisher be registered.  https://jira.jboss.org/jira/browse/JBESB-2913 seems to cover this.

I spent a good amount of time digging through when/how/why publishers are added to ServicePublisher, as well as when/how/why EPRs are registered in the Registry, as well as how/why the contract JSP application exposes contracts.  Basically, there are two kinds of Publishers: ContractPublishers and ContractReferencePublishers.  When you are talking about EBWS or SOAPProxy, a ContractReferencePublisher is added, and they do not require an EPR registered in the Registry.  However, everything else (like SOAPProducer) requires an EPR registered in the Registry for them to display properly in the contract JSP application.

You can't not register their EPRs, just so the contract JSP app won't display them.  Reason is that a particular Service might have multiple Listeners configured, for example a mix of JMS and HTTP (JBR or HttpGateway), and not registering the non-HTTP EPRs would mean the ServiceInvoker would have nothing to load balance across.  Because of this, I believe the best route to take is to change the contract JSP app so that it lists all Services, but only provides contract links to WSDL for HTTP (or HTTPS) endpoints.

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4270282#4270282

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4270282