Anyone ever have trouble with SOAP headers going from .NET to JEE (Axis)

Anyone ever have trouble with SOAP headers going from .NET to JEE (Axis)

Old forum URL: forums.lhotka.net/forums/t/10501.aspx


ltgrady posted on Thursday, July 07, 2011

I have a CSLA (2.x) web app and we created a few webservices for our clients.  All of our credentials for authentication are passed in using the SOAP header.  So far everything works great.


We have a new developer/customer who is developing with Axis2 and trying to consume the web service (I think he is trying Maven to create the proxy) and no matter what we try the SOAP headers are not showing up in the proxy.

I have googled around and it appears that .NET generates the wsdl with implicit soap headers (information not in the portType) and not the explicit headers that java needs.  I'm having the worst time trying to find a work around to fix my wsdl generated by .NET.

Has anyone experienced this?  Found a fix?

Copyright (c) Marimer LLC