axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim K. (Gmane)" <tkgmane...@ugcs.net>
Subject Re: forcing registration of serializer/deserializer for beans that do not appear directly as args
Date Wed, 16 Feb 2005 20:12:53 GMT
Yes, I do. Ah, I missed the --extraClasses option ...

Do I need to also include anything special for the arrays to work (e.g.a 
B[] in addition to B)?

Thanks.

Tim

Sebastien Mayemba Mbokoso wrote:
> Do you know all the object types of 'Object o' at run-time ? If you do
> maybe you can use
> Java2WSDL with that more option : --extraClasses ?
> 
> -----------
> Sebastien
> 
> 
> On Wed, 16 Feb 2005 11:20:24 -0800, Tim K. (Gmane) <tkgmane+at@ugcs.net> wrote:
> 
>>Hello,
>>
>>Using java2wsdl to generate the WSDL from java server side classes, how
>>can I force the registration of a serializer/deserializer for a bean
>>that does not appear directly in the method arguments, e.g.:
>>
>>public A foo(A a)
>>
>>where A is a bean which can contain another bean B and also a bean array
>>B[] but it's not typed (e.g. it's defined as an Object):
>>
>>A
>>{
>>   ...
>>   Object o;  // At run-time this can be B, B[] or other things.
>>   ...
>>}
>>
>>The problem is that at run-time the server complains that there is no
>>deserializer for B which makes sense because java2wsdl has never seen B
>>anywhere in the method signatures.
>>
>>The work-around so far has been to add a dummy method that has both B
>>and B[] as arguments, but there's gotta be a nicer way to do it.
>>
>>Thank you for your help.
>>
>>--
>>Tim
>>
>>
> 
> 


Mime
View raw message