ain.
Scott
- Original Message -
From: "Soumen Sarkar" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, April 03, 2002 1:57 PM
Subject: RE: SOAP ObjecT support
> I beleive a definite answer on this issue is needed to foster SOAP interop.
> I would v
estrictions within Apache
SOAP that prevent the use of such names. Therefore, I would expect the
serializer to create such names.
Scott Nichol
- Original Message -
From: "Soumen Sarkar" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, April 02, 2002 9:20
strictions within Apache SOAP that prevent the use of such names.
Therefore, I would expect the serializer to create such names.
Scott Nichol
- Original Message -
From: "Soumen Sarkar" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, April 02, 2002 9:20 PM
S
Nichol [mailto:[EMAIL PROTECTED]]
Sent: Sunday, March 31, 2002 8:18 PM
To: [EMAIL PROTECTED]
Subject: Re: SOAP ObjecT support
Apache SOAP can work with any Java class you can create. If the class is a
bean, the BeanSerializer can be used to write/read an instance to/from a
SOAP message. If the
Apache SOAP can work with any Java class you can create. If the class is a
bean, the BeanSerializer can be used to write/read an instance to/from a
SOAP message. If the class is not a bean, a custom serializer and/or
de-serializer is written. The AddressBook example shows how to use
user-define
