Null binding for SOAP action issue with SOAPProxy

Solution Unverified - Updated -

Issue

  • I am using SOAPProxy to dynamically call web services. The properties for SOAPProxy are “wsdl” and “soapaction”. SOAPProxy parses a WSDL at runtime and tries to map a soapaction to a binding before in order to call the service address. My understanding is that every binding maps to an operation and a soapaction.
  • SOAPProxy finds both binding and soapaction while initializing but at the time it is about to make the call it logs that the binding for that soapaction is null. When this happens, it uses the root element of the request as the operation and tries to find a binding for that operation.
INFO  [SOAPProxy] mapped soapaction ["http...action"] to binding [{http...binding}BindingName]
INFO  [SOAPProxy] mapped soapaction ["http...action"] to binding [{http...binding}BindingName]
INFO  [SOAPProxy] mapped operation [{http...binding}Operation] to binding [{http...binding}BindingName]
INFO  [SOAPProxy] mapped binding [{http...binding}BindingName] to transport [org.jboss.soa.esb.actions.soap.proxy.HttpSOAPProxyTransport] with endpoint address: [http...serviceEndpoint]
INFO  [CustomInvoker] start [ SOAPProxy ] process()…
WARN  [SOAPProxy] null binding for soapaction [http...action]; parsing envelope to discover operation...

Environment

  • Red Hat JBoss SOA Platform (SOA-P)
    • 5.x
    • 4.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.