Bryan,
I think that I confused you a little. My apologies. I now believe that you
can use the BeanSerializer just fine.
If you are interested in using XML literal, you just need to have your SOAP
Service method take in an org.w3c.dom.Element as a parameter. And in your
client you need to specify the encoding style of of the Call by doing
something like this.
mycall.setEncodingStyleURI(Constants.NS_URI_LITERAL_XML);
then you can create your Parameter with the XML Literal encoding style like
this.
myParameter.addElement(new Parameter("request", Element.class,
myElementToPass, Constants.NS_URI_LITERAL_XML));
After all this, I think that you might still be better off going with your
original thought of using the BeanSerializer. Sorry again for the
confusion.
Craig
-----Original Message-----
From: Bryan Field [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 13, 2001 3:30 PM
To: [EMAIL PROTECTED]
Subject: RE: xml schemas?
Craig,
Just for clarification, If I am not using the BeanSerializer then I will
have to encode and decode the message by creating my own code, right? Are
there any standard libraries out there for this or do you just create you
own?
Thanks,
Bryan
-----Original Message-----
From: Wilkins, Craig [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 13, 2001 6:42 AM
To: '[EMAIL PROTECTED]'
Subject: RE: xml schemas?
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
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.303 / Virus Database: 164 - Release Date: 11/24/2001
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.303 / Virus Database: 164 - Release Date: 11/24/2001
