Example workaround for now:
In case you get a strange behavior while testing, please test this:
BC-SOAP needs a parameter called SoapAction, unique to each operation. When you generate WSDLs for Jsr181 in Petals Studio, Each operation has the same SoapAction value. This should be fine in our case. But to be completely clear in case of strange behavior, you can edit HelloWorld.wsdl and define _SoapAction_s. This might be corrected in the future, in Petals Studio or in BC-SOAP.
SELECT:
<operation name="helloWorld">
<soap:operation soapAction=""/>
REPLACE BY:
<operation name="helloWorld">
<soap:operation soapAction="helloWorld"/>
SELECT:
<operation name="listenToTheWorld">
<soap:operation soapAction=""/>
REPLACE BY:
<operation name="listenToTheWorld">
<soap:operation soapAction="helloWorld"/>
Bug
Resolved
Minor
