Let's say that SomeXObject has the following structure:
Class SomeXObject {
private int anInt;
private Date anyDate;
}
This object itself, when it is generated on the client side using WSDL2Java,
the latter will replace Date by Calendar and add some additional methods
specific to Axis! Although the generated object ressembles a lot to the
ORIGINAL SomeXObject used on the server, it is NOT the same, and thus for
example server-side CAST operations will fail if this object is sent back to
the server via another communication channel (like JMS)
Knowing that I control perfectly the code generation on the client-side, is
there any possibility to tell the code generator, not to generate another
copy of SomeXObject and besides, use the one I am giving him in a *.jar lib
or something? This way, I will be able to use SomeXObject retreived via a
webservice on a JMS Topic to send it back to the server for another purpose!
(NOTE: I need both WebServices and JMS between the client and the server)
Thanks
Fady
----- Original Message -----
From: "Paul Callahan" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, September 14, 2004 2:40 PM
Subject: Re: WSDL2Java issue
> whats in SomeXObject? what is being generated--in addition to what
> should be there?
>
>
> ----- Original Message -----
> From: Fady Kaddoum <[EMAIL PROTECTED]>
> Date: Tue, 14 Sep 2004 09:15:56 +0200
> Subject: WSDL2Java issue
> To: [EMAIL PROTECTED]
>
>
> Hello everybody!
>
> I 've developped some services that have the following format in general:
>
> public SomeXObject[] getAllXObjects() {
> ...
> }
>
> I generate the client Stub using WSDL2Java and everythings works fine.
> On the other hand, on the client side, I get a different
> implementation of the Java Bean "SomeXObject" than the one on the
> server. Is it possible to do it in a way as to keep on the client the
> same implementation of "SomeXObject" as the one on the server! It
> doesn't matter if additional Axis stuff are generated in other
> classes!
>
> Thanks
> Fady
