your XObject goes over the wire as xml representing the information contained within in - the XObject implementation specifics arent carried across.
/t -----Original Message----- From: Paul Callahan [mailto:[EMAIL PROTECTED] Sent: Tuesday, September 14, 2004 2:40 PM To: [EMAIL PROTECTED] 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
