You make a good point. I was thinking that unless you had the Apache SOAP using BeanSerializer on both client and server, it would be real tough. The email that followed yours from Guy, cleared up that confusion as he does it with SOAP Lite.
However, can your bean contain other beans and still work with the BeanSerializer? For instance, can you have a car bean that has 4 tire bean members or some List of Passengers Beans? Will this work with the BeanSerializer? -----Original Message----- From: John Mani [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 12, 2001 8:42 PM To: [EMAIL PROTECTED] Subject: Re: xml schemas? > What data types are the parameters to the methods? If they are just a set > of strings, I advise you not to use the BeanSerializer, as that would > require that your client either use the BeanSerializer or know how to > encode/decode the SOAP body in such a way that the BeanSerializer knows how > to deserialize at the server. If your clients are not using Apache SOAP, > then using the BeanSerializer is a lot of work for them. AFAIK, the BeanSerializer serializes a JavaBean into regular SOAP encoding, so you ought not to have any problems using the BeanSerializer. I have been succesfully using the BeanSerializer to serialize/deserialize Java objects between Apache SOAP and WebLogic. The BeanSerialier on the Apache side, and WebLogic's own stuff on that other side. What interoperability problems have you had with the BeanSerializer ? -john
