0 Replies Latest reply on Jan 24, 2008 9:06 AM by Luc De pauw

    Unable to consume webservice with empty SOAPAction with SOAP

    Luc De pauw Newbie

      Hi,

      In my code I already consumed webservices with a SOAPAction defined without problems. When I try to access an external webservice which is defined in the wsdl as this: (soapAction is empty string)

      <wsdl:operation name="send">
       <wsdlsoap:operation soapAction=""/>
       <wsdl:input name="sendRequest">
       <wsdlsoap:body use="literal"/>
       </wsdl:input>
       <wsdl:output name="sendResponse">
       <wsdlsoap:body use="literal"/>
       </wsdl:output>
       <wsdl:fault name="DslParseException">
       <wsdlsoap:fault name="DslParseException" use="literal"/>
       </wsdl:fault>
       </wsdl:operation>
      
      


      I can not deploy my esb, it fails in parsing the jboss-esb.xml

      jboss-esb.xml snippet

       <action name="soapui-client" class="org.jboss.soa.esb.actions.soap.SOAPClient">
       <property name="wsdl" value="${url.services.web.sendmail}"/>
       <property name="operation" value="send"/>
       <property name="SOAPAction" value=""/>
       </action>
      


      stacktrace snippet

       at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC
      onstructorAccessorImpl.java:27)
       at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
       at org.jboss.soa.esb.listeners.message.ActionProcessorMethodInfo.getActi
      onClassInstance(ActionProcessorMethodInfo.java:344)
       ... 54 more
      Caused by: org.jboss.soa.esb.ConfigurationException: Required configuration prop
      erty 'SOAPAction' not defined on configuration 'action'.
       at org.jboss.soa.esb.helpers.ConfigTree.getRequiredAttribute(ConfigTree.
      java:242)
       at org.jboss.soa.esb.actions.soap.SOAPClient.<init>(SOAPClient.java:251)
      
       ... 58 more
      14:26:36,484 INFO [TomcatDeployer] deploy, ctxPath=/activation, warUrl=.../tmp/
      


      Does someone know how to config this in the jboss-esb.xml ?

      Running the request from soapui works fine.

      Regards

      Luc