axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Gainty" <>
Subject Re: Axis2/POJO: Caveats with data classes?
Date Tue, 08 May 2007 01:43:48 GMT
Hello Jeremy

assuming you're working with AXIS2 v1.1 available at
There exists a configuration for the service at the bottom of 
which should display a series of parameter definitions which define the pojo 

here is one an example which identifies a POJO named 

the examples from axis-2.1.1 specifically 
axis2-1.1\rampart-1.1\axis2-1.1\samples\pojoguide\README.txt should explain

//Building the Service
$ant from Axis2_HOME/samples/pojoguide

//Running the Client
$ant rpc.client

This email message and any files transmitted with it contain confidential
information intended only for the person(s) to whom this email message is
addressed.  If you have received this email message in error, please notify
the sender immediately by telephone or email and destroy the original
message without making a copy.  Thank you.

----- Original Message ----- 
From: "Jeremy" <>
To: <>
Sent: Monday, May 07, 2007 9:25 PM
Subject: Axis2/POJO: Caveats with data classes?

> I've got a POJO-based service running.  In the same package as the service 
> class, I also have some public data classes that are used by the service. 
> This one method I am testing accepts one of the data classes (User) as a 
> parameter.  Whenever this method is invoked via SOAP, the parameter comes 
> up as null (which eventually leads to a NullPointerException and then to a 
> java.lang.reflect.InvocationTargetException) despite the fact that it was 
> passed in via SOAP.
> Is there a reason for this?  The User type shows up just fine in the WSDL, 
> and the client (SOAPScope) clearly doesn't see anything wrong until the 
> SOAP fault comes back.  Is there something else I need to do to make these 
> data classes usable from SOAP?  I tried invoking my service method 
> manually through a java program and everything went fine - so it's 
> somewhere in the SOAP dispatcher that things are going wrong.
> I thought this might be a common problem so I'd ask the mailing list.  Any 
> ideas?  I'm kind of an Axis/Tomcat newbie (in case it wasn't obvious) but 
> I'm pretty well-versed with Java.
> Thanks,
> Jeremy
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message