Can SOAP Action be customized to match SOAP body element name?

[Sillves]

Hi,
I have a question about SOAP Action handling in Microcks. When I import a WSDL, the SOAP Action (from the WSDL) and the actual SOAP body element name don't always match.
For example:

SOAP Action in WSDL: http://xxxxxxx.xxxx/ListAll
First element in SOAP body envelope:

This means that when I send a request with in the body, Microcks expects the SOAP Action to be something like ListAll based on the body element, rather than the actual http://xxxxxxx.xxxx/ListAll from the WSDL.
Is there a way to configure Microcks to match requests based on the SOAP Action header from the WSDL, rather than deriving it from the body element name? Or do I need to ensure these always match in my WSDL?
Thanks!

[lbroudoux]

Hey,

The matching of the target operation is done as follows on incoming request:

1. Microcks tries to extract the Soap Action
   1.1 First, looking at the action indicator in the content type header, if it's SOAP 1.2
   1.2 Then, looking at the SOAPAction header, if it's SOAP 1.1 or older
2. If a Soap Action is found, then we compare it to the action property of the discovered operations (from the action in the WSDL) to find the corresponding operation
3. If no Soap Action found above, then it tries to extract the operation name from the SOAP payload, looking at the child tag name under <soap:Body>

Hope it helps,