Axis2 Client encoding message problem

Question

Hi Experts,
I developed an application (EAR + WEB + LIB) acting as a Webservice proxy for a healthcare service. Abap calls my proxyservice which then calls the other service. This application is developed as maven2 project with axis2 and dependent lib to be used in any servletcontainer.
Deploying the proxyserver on a Jetty or Tomcat works fine, all the SOAP messages are transferred like expected (including Faults and Umlauts)
Deploying the proxyserver an a Netweaver CE 7.1 system also works but there are two issues and i cannot find the reason:
1.) When my proxyserver gets the answer from the healthcare service, the SOAP Response holds a correctly encoded UTF-8 String with german Umlaut (ÜÖÄ...), but my generated Webservice Stub always gets a "null" instead of the german Umlaut. Debugging into the generated Stub and even into the Axis Sourcecode shows me that the Soap request seems to be incorrect when it arraves at the axis sourcecode, so i think something between Axis and the CE 7.1 Server is doing wrong.
I loked also in NetWeaver Administrator and can see that classloading works as expected.
2.) When my proxyserver gets a SOAP Fault from the healthcare service it arrives without the Fault details.
Both issues look to me as if there is a software layer between my Axis2 Servlet and the underlying Server doing something with my http requests/responses.
Does anybody know how i could proceed?
Regards
Michael

Answer 1

thanks for the response.
I was using Axis2 1.2 and Rampart 1.2
I got it partially working.
I got rid of the Sign.xml and used Auth.xml only in my webservice.
Axis2 was generating the wrong namespace for most of my parameter Bean classes...I had to modify those by hand. I was able to finally access about 90% of my webservice methods but a few still threw the error 'unable to parse incoming request'.
I thought moving to Axis2 1.3 might fix the namespace issue but then that requires Rampart 1.3
I gave up...Clientgen just works, without all of these problems. I would like to provide a client solution for my customers that is not dependent upon BEA weblogic.jar, but Axis2 does not work with WS-Policy enabled webservice running on BEA.