Hi Alon,
The reason is that the Axis2 system uses the SOAPAction to find the service on the server side. As soon as the SOAP action went missing , the service would  not be found!
If you look inside the generated  message receiver code, you'll see what I mean.
The problem with just filling out what the code generator generated code may not solve the problem because the old client options code had a bug in delegating. So you should modify the code NOT to have a parent options passed in and then set the SOAPAction.

Ajith

Reply via email to