I am throwing an exception from server side but on the client side the
exception object has all the fields set to NULL. I checked the incoming SOAP
fault message and it has correct values for the fields. I believe the
correct jar files are not being used because I had a similar problem in
sending List data types as parameters and it was fixed by adding asm.jar. I
am using Wrapped Doc/Lit with the following dependencies on client:
--------------------------------------------------------------------------------------------------
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>4.1</version>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>org.apache.cxf</groupId>
<artifactId>cxf-rt-frontend-jaxws</artifactId>
<version>${cxf.version}</version>
</dependency>
<dependency>
<groupId>org.apache.cxf</groupId>
<artifactId>cxf-rt-transports-http</artifactId>
<version>${cxf.version}</version>
</dependency>
<dependency>
<groupId>asm</groupId>
<artifactId>asm</artifactId>
<version>3.0</version>
</dependency>
--------------------------------------------------------------------------------------------------
If it really is a problem with using the correct jar files, it will be very
helpful to get a list of jars that need to be used on server and client side
to enable web service using CXF. I read the <KNOWN_JARS> file that is part
of CXF download, but adding them has not solved my problem. Can someone
point out which classes are absolutely needed to handle fault/exception
objects properly?
Thanks,
Kannan
--
View this message in context:
http://www.nabble.com/Exception-object-has-all-fields-set-to-NULL-on-client-side-tp14723440p14723440.html
Sent from the cxf-user mailing list archive at Nabble.com.
