Service.xml with JAXWSDeployerSupport / messagfilter as module / logging request, responses

2017-02-09 Thread d.ku...@technisat.de
Hey, hopefully you guys can give me a hint. I moved one of our applications from axis2 1.4 to axis2 1.7.4. Currently I'm using the JAXWS approach. Our Webservice is annotated with: @WebService -->Deployment is successfully. So far it looks like the service.xml is completely ignored while using

The input stream for an incoming message is null.

2017-02-09 Thread d.ku...@technisat.de
Hey, another problem. In my aqxis2 project I'm calling a asp.net soap service. Serviceclient ist generated vie wsimport. Because the axis2 code generator gave me faulty class. --> wants to implement a class not a interface... -> how ever I used wsimport. After calling -net soap Service I'm getti

AW: The input stream for an incoming message is null.

2017-02-09 Thread d.ku...@technisat.de
Update: If i'm generating a axis (axis1) client with eclipse everything is okay.. Any ideas? Mit freundlichen Grüßen David Kumar Senior Software Engineer Java, B. Sc. Projektmanager PIM Abteilung Infotech TechniSat Digital GmbH Julius-Saxler-Straße 3 TechniPark D-54550 Daun / Germany Tel.: +