axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anne Thomas Manes" <>
Subject Re: Complex type problem
Date Thu, 25 May 2006 12:52:05 GMT
I think you need to use a beanmapping element rather than a typemapping
If that doesn't work, please post more information.


On 5/25/06, Roy <> wrote:
> Hello all,
> I have deployed an ejb service with a method that takes as input a complex
> object (it contains 2 Strings and one int var). When i generate the code in
> the client with WSDL2Java and call the method i can see that this complex
> type object becomes null. I can see in the monitor that the request object
> isn't null but in the debug mode i can see that the service receives a null
> object. This problem doesn't occur when I use simple types to transfer.
> I tried the same code on a non-ejb service and works normally.
> In the deploy wsdd i use a typemapping element to describe the object and
> i use the BeanSerializerFactory and BeanDeSerializer factory as
> serializer-deserializer.
> Can someone explain why is this happening?
> Regards,
> Roy
> ------------------------------
> Χρησιμοποιείτε Yahoo!
> Βαρεθήκατε τα ενοχλητικά μηνύ ματα (spam); Το Yahoo!
Mail διαθέτει την
> καλύτερη δυνατή προστασία κατά των ενοχλητικών
View raw message