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

[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 
annotations?
It doesn't matter what ever I'm changing into service.xml --> no effect.

Bevor upgrading we had a module for logging -->  The target is to log every 
incoming / outgoing message.
We defined that module at the service.xml. as messageReceivers:

 
   http://www.w3.org/2004/08/wsdl/in-only"; 
class="org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver" />
   http://www.w3.org/2004/08/wsdl/in-out";  
class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/>
 


At the logs I can see the modules is loaded..
12:27:25:835 - INFO - ModuleDeployer - Deploying module: addressing-1.7.4 - 
file:/C:/projects/workspaces/java_64bit/.metadata/.plugins/org.eclipse.wst.server.core/tmp5/wtpwebapps/axis2/WEB-INF/modules/addressing-1.7.4.mar
12:27:25:841 - INFO - ModuleDeployer - Deploying module: jaxws-1.7.4 - 
file:/C:/projects/workspaces/java_64bit/.metadata/.plugins/org.eclipse.wst.server.core/tmp5/wtpwebapps/axis2/WEB-INF/modules/axis2-jaxws-mar-1.7.4.mar
12:27:25:848 - INFO - ModuleDeployer - Deploying module: logging - 
file:/C:/projects/workspaces/java_64bit/.metadata/.plugins/org.eclipse.wst.server.core/tmp5/wtpwebapps/axis2/WEB-INF/modules/logging.mar
12:27:25:861 - INFO - ModuleDeployer - Deploying module: metadataExchange-1.7.4 
- 
file:/C:/projects/workspaces/java_64bit/.metadata/.plugins/org.eclipse.wst.server.core/tmp5/wtpwebapps/axis2/WEB-INF/modules/mex-1.7.4.mar
12:27:25:868 - INFO - ModuleDeployer - Deploying module: mtompolicy-1.7.4 - 
file:/C:/projects/workspaces/java_64bit/.metadata/.plugins/org.eclipse.wst.server.core/tmp5/wtpwebapps/axis2/WEB-INF/modules/mtompolicy-1.7.4.mar
12:27:25:874 - INFO - ModuleDeployer - Deploying module: ping-1.7.4 - 
file:/C:/projects/workspaces/java_64bit/.metadata/.plugins/org.eclipse.wst.server.core/tmp5/wtpwebapps/axis2/WEB-INF/modules/ping-1.7.4.mar
12:27:25:878 - INFO - ModuleDeployer - Deploying module: script-1.7.4 - 
file:/C:/projects/workspaces/java_64bit/.metadata/.plugins/org.eclipse.wst.server.core/tmp5/wtpwebapps/axis2/WEB-INF/modules/scripting-1.7.4.mar
12:27:26:292 - INFO - JAXWSDeployerSupport - Deploying JAXWS annotated class 
de.technigroup.axis2.customer.CRMCustomerService as a service - 
nullCRMCustomerService

As the Service.xml is completely ignored, logging doesn't work anymore.
I also tried to put the receivers into axis2.xml, above  the default ones. --> 
without success.

   http://www.w3.org/2004/08/wsdl/in-only";

class="org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver" />
   http://www.w3.org/2004/08/wsdl/in-out";

class="org.apache.axis2.rpc.receivers.RPCMessageReceiver" />
http://www.w3.org/2004/08/wsdl/in-only";
 
class="org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver"/>
http://www.w3.org/2004/08/wsdl/in-out";
 
class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/>
http://www.w3.org/2006/01/wsdl/in-only";
 
class="org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver"/>
http://www.w3.org/2006/01/wsdl/in-out";
 
class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/>
http://www.w3.org/ns/wsdl/in-only";
 
class="org.apache.axis2.receivers.RawXMLINOnlyMessageReceiver"/>
http://www.w3.org/ns/wsdl/in-out";
 
class="org.apache.axis2.receivers.RawXMLINOutMessageReceiver"/>




Anyone an Idea why how to get logging back to work?
I also tried to write a provider to log the message, without success.. Any 
other ideas?



David Kumar

The input stream for an incoming message is null.

[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 getting:

The input stream for an incoming message is null.

At the other hand the .net service is never called.

Anny ideas?
I found something about options.. But in this client (@WebServiceClient) I'cant 
add these options.

options.setProperty(Constants.Configuration.DISABLE_SOAP_ACTION,Boolean.TRUE);


David Kumar

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

[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.: + 49 (0) 6592 / 712 -2826
Fax: + 49 (0) 6592 / 712 -2829

www.technisat.com/de_DE/
www.facebook.com/technisat

Von: David Kumar
Gesendet: Donnerstag, 9. Februar 2017 15:46
An: 'java-user@axis.apache.org'
Betreff: The input stream for an incoming message is null.

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 getting:

The input stream for an incoming message is null.

At the other hand the .net service is never called.

Anny ideas?
I found something about options.. But in this client (@WebServiceClient) I'cant 
add these options.

options.setProperty(Constants.Configuration.DISABLE_SOAP_ACTION,Boolean.TRUE);


David Kumar