Axis2 to Metro conversion adds new elements

Axis2 to Metro conversion adds new elements

We recently converted/migrated an existing Axis2 webservice over to Metro and
it all deploys successfully. We've encountered an issue during testing
because the soap request/response structure is slightly different.

Re: Axis2 to Metro conversion adds new elements

I'm not sure but that soap action value
"GetBookInfoByISBN/GetBookInfoByISBN" seems strange to me, I'm not used
to slashes in soapAction values (may be legit, I don't know). Does the
problem occur if you change the soapAction to one without slashes?

Re: Axis2 to Metro conversion adds new elements

Thanks for the response Glen, I appreciate it!

It's interesting you mentioned that soapAction b/c after posting to this
forum I tried exactly what you asked and it made no different. The additional
<GetBookInfoByISBN> element is still inserted into the soap request
structure. For example:

Do you know if I can fix these issues I've discussed with annotations? I was
able to get rid of the <arg0> element in the soap request but that then
disrupts the service method parameter from binding. So my service method then
throws a NullPointerException b/c the parameter it's expected to use is null.