You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@xml.apache.org by Olivier Brand <ol...@intraware.com> on 2001/02/27 20:54:48 UTC
Writing new Serializer/Deserializer
I am just wondering if it would be interesting (possible ?) to add new
Serializers/Deserializers to the SOAP package ?
I have created 2 interesting ones:
- A DOM serializer/deserializer (util tools exist but there are no
serializers available in the current package)
- A Castor-XML serializer/deserializer. This one uses the amazing
Exolab.org Castor package. For people who don't know, this is similar to
the Javasoft JAXB specification. You can start from an XSD Schema and
create a full Java framework from it. No need to use DOM or SAX anymore
! This serializer/deserializer allows to pass very complex types
constrained by an XSD Schema and receive on the server side the same
type.
Any interests ?
Olivier
Re: Writing new Serializer/Deserializer
Posted by Olivier Brand <ol...@intraware.com>.
This why I have created the DOMSerializer. You could treat on the server complex
java objects created by Castor but issue and receive mostly only XML using the
DOMSerializer. Now if your client is something else than Java, it doesn't matter
since the enveloppe contains anyway only XML. The Castor marshalling process
creates an XML document which repesents the original document. This is a bridge
Java <----> XML. I am pretty sure that Microsoft will come with such tool (a
Schema compiler).
Olivier
Erik van Zijst wrote:
> On Tuesday 27 February 2001 20:54, you wrote:
>
> > > I am just wondering if it would be interesting (possible ?) to add new
> > Serializers/Deserializers to the SOAP package ?
> >
> > I have created 2 interesting ones:
> >
> > - A DOM serializer/deserializer (util tools exist but there are no
> > serializers available in the current package)
> > - A Castor-XML serializer/deserializer. This one uses the amazing
> > Exolab.org Castor package. For people who don't know, this is similar to
> > the Javasoft JAXB specification. You can start from an XSD Schema and
> > create a full Java framework from it. No need to use DOM or SAX anymore
> > ! This serializer/deserializer allows to pass very complex types
> > constrained by an XSD Schema and receive on the server side the same
> > type.
>
> And what if the client is a C# app or anything else build by a third party
> without that package? Could they interprete and unmarshall the complex types?
>
> Erik
> --
> Experience, n.:
> Something you don't get until just after you need it.
> -- Olivier
Re: Writing new Serializer/Deserializer
Posted by Olivier Brand <ol...@intraware.com>.
This why I have created the DOMSerializer. You could treat on the server complex
java objects created by Castor but issue and receive mostly only XML using the
DOMSerializer. Now if your client is something else than Java, it doesn't matter
since the enveloppe contains anyway only XML. The Castor marshalling process
creates an XML document which repesents the original document. This is a bridge
Java <----> XML. I am pretty sure that Microsoft will come with such tool (a
Schema compiler).
Olivier
Erik van Zijst wrote:
> On Tuesday 27 February 2001 20:54, you wrote:
>
> > > I am just wondering if it would be interesting (possible ?) to add new
> > Serializers/Deserializers to the SOAP package ?
> >
> > I have created 2 interesting ones:
> >
> > - A DOM serializer/deserializer (util tools exist but there are no
> > serializers available in the current package)
> > - A Castor-XML serializer/deserializer. This one uses the amazing
> > Exolab.org Castor package. For people who don't know, this is similar to
> > the Javasoft JAXB specification. You can start from an XSD Schema and
> > create a full Java framework from it. No need to use DOM or SAX anymore
> > ! This serializer/deserializer allows to pass very complex types
> > constrained by an XSD Schema and receive on the server side the same
> > type.
>
> And what if the client is a C# app or anything else build by a third party
> without that package? Could they interprete and unmarshall the complex types?
>
> Erik
> --
> Experience, n.:
> Something you don't get until just after you need it.
> -- Olivier
Re: Writing new Serializer/Deserializer
Posted by Erik van Zijst <er...@marketxs.com>.
On Tuesday 27 February 2001 20:54, you wrote:
> > I am just wondering if it would be interesting (possible ?) to add new
> Serializers/Deserializers to the SOAP package ?
>
> I have created 2 interesting ones:
>
> - A DOM serializer/deserializer (util tools exist but there are no
> serializers available in the current package)
> - A Castor-XML serializer/deserializer. This one uses the amazing
> Exolab.org Castor package. For people who don't know, this is similar to
> the Javasoft JAXB specification. You can start from an XSD Schema and
> create a full Java framework from it. No need to use DOM or SAX anymore
> ! This serializer/deserializer allows to pass very complex types
> constrained by an XSD Schema and receive on the server side the same
> type.
And what if the client is a C# app or anything else build by a third party
without that package? Could they interprete and unmarshall the complex types?
Erik
--
Experience, n.:
Something you don't get until just after you need it.
-- Olivier
Re: Writing new Serializer/Deserializer
Posted by Erik van Zijst <er...@marketxs.com>.
On Tuesday 27 February 2001 20:54, you wrote:
> > I am just wondering if it would be interesting (possible ?) to add new
> Serializers/Deserializers to the SOAP package ?
>
> I have created 2 interesting ones:
>
> - A DOM serializer/deserializer (util tools exist but there are no
> serializers available in the current package)
> - A Castor-XML serializer/deserializer. This one uses the amazing
> Exolab.org Castor package. For people who don't know, this is similar to
> the Javasoft JAXB specification. You can start from an XSD Schema and
> create a full Java framework from it. No need to use DOM or SAX anymore
> ! This serializer/deserializer allows to pass very complex types
> constrained by an XSD Schema and receive on the server side the same
> type.
And what if the client is a C# app or anything else build by a third party
without that package? Could they interprete and unmarshall the complex types?
Erik
--
Experience, n.:
Something you don't get until just after you need it.
-- Olivier
Re: Writing new Serializer/Deserializer
Posted by Olivier Brand <ol...@intraware.com>.
I am not sure, but it seems that the WSTK doesn't handle complex or custom types.
The best option might be to use the WSTK to parse a WSDL file, and build a
framework around Castor.
Olivier
"John E. Conlon" wrote:
> At this point I am still educating myself as to the choices for
> serializing technologies. I like what I have seen in the Castor, but it
> seems that WSDL and IBM's WSTK may also be a fit here.
>
> How would compare WSTK to the Castor approach.
>
> John
>
> At 09:17 AM 3/1/01 -0800, you wrote:
> >For example, in the case of implementing a Java client ans a specific service
> >(in Java) runiing on the SOAP server, if you are exchanging XML data like the
> >UDDI protocol is doing, you don't want to write your
> marshaller/unmarshaller for
> >each object, so using Castor helps a lot since it is generating everything
> for
> >you.
> >Now you have 2 options:
> >
> >- Sending the XML yourself through SOAP and change the signature of the
> >operation to String or Element
> >- Writing your Castor Serializer/Deserializer and having the SOAP server
> >marshalling/unmarshalling the XML for you. So your signature will be strongly
> >typed, like PurchaseOrder for example. (PurchaseOrder being a Castor
> generated
> >Class representing an element in your XSD Schema definition).
> >
> >I have decided to write a CastorSerializer class and a DOM one as well. So
> the
> >service can use a Java Castor Object and the Client receiving an XML
> document as
> >a String, in case the caller is not Java. Then if it is Java, you can just
> use
> >Castor and the unmarshall method to re-initialize the object.
> >
> >Hope it is clear enough. Looking at the source code of the Date serializer
> >helped me a lot. There a still some questions regarding the encodingStyle. I
> >have posted a question about it earlier.
> >
> >Olivier
> >
> >"John E. Conlon" wrote:
> >
> >> Your original post and the one concerning business logic validation
> >> prompted me
> >> to look into Castor and do some experimenting. It looks very good. Can
> you
> >> share some examples of how you work with SOAP and Castor?
> >>
> >> thanks,
> >>
> >> John
> >>
> >> At 11:54 AM 2/27/01 -0800, you wrote:
> >> >
> >> > I am just wondering if it would be interesting (possible ?) to add new
> >> > Serializers/Deserializers to the SOAP package ?
> >> >
> >> > I have created 2 interesting ones:
> >> >
> >> > - A DOM serializer/deserializer (util tools exist but there are no
> >> > serializers available in the current package)
> >> > - A Castor-XML serializer/deserializer. This one uses the amazing
> >> > Exolab.org Castor package. For people who don't know, this is similar to
> >> > the Javasoft JAXB specification. You can start from an XSD Schema and
> >> > create a full Java framework from it. No need to use DOM or SAX anymore
> >> > ! This serializer/deserializer allows to pass very complex types
> >> > constrained by an XSD Schema and receive on the server side the same
> >> > type.
> >> >
> >> > Any interests ?
> >> >
> >> > Olivier
> >> >
> >> > <file://c:\opt\qualcomm\eudora
> >> > mail\attach\olivier17.vcf>12d7ff0f.jpg<file://c:\opt\qualcomm\eudora
> >> > mail\attach\olivier17.vcf> olivier17.vcf
> >
> >
> ************************************************************************
> John E. Conlon
> jconlon@verticon.com
> tel: (770) 886-5470
> fax: (770) 888-6894
> <http://www.verticon.com/>www.verticon.com
> ************************************************************************
Re: Writing new Serializer/Deserializer
Posted by Olivier Brand <ol...@intraware.com>.
I am not sure, but it seems that the WSTK doesn't handle complex or custom types.
The best option might be to use the WSTK to parse a WSDL file, and build a
framework around Castor.
Olivier
"John E. Conlon" wrote:
> At this point I am still educating myself as to the choices for
> serializing technologies. I like what I have seen in the Castor, but it
> seems that WSDL and IBM's WSTK may also be a fit here.
>
> How would compare WSTK to the Castor approach.
>
> John
>
> At 09:17 AM 3/1/01 -0800, you wrote:
> >For example, in the case of implementing a Java client ans a specific service
> >(in Java) runiing on the SOAP server, if you are exchanging XML data like the
> >UDDI protocol is doing, you don't want to write your
> marshaller/unmarshaller for
> >each object, so using Castor helps a lot since it is generating everything
> for
> >you.
> >Now you have 2 options:
> >
> >- Sending the XML yourself through SOAP and change the signature of the
> >operation to String or Element
> >- Writing your Castor Serializer/Deserializer and having the SOAP server
> >marshalling/unmarshalling the XML for you. So your signature will be strongly
> >typed, like PurchaseOrder for example. (PurchaseOrder being a Castor
> generated
> >Class representing an element in your XSD Schema definition).
> >
> >I have decided to write a CastorSerializer class and a DOM one as well. So
> the
> >service can use a Java Castor Object and the Client receiving an XML
> document as
> >a String, in case the caller is not Java. Then if it is Java, you can just
> use
> >Castor and the unmarshall method to re-initialize the object.
> >
> >Hope it is clear enough. Looking at the source code of the Date serializer
> >helped me a lot. There a still some questions regarding the encodingStyle. I
> >have posted a question about it earlier.
> >
> >Olivier
> >
> >"John E. Conlon" wrote:
> >
> >> Your original post and the one concerning business logic validation
> >> prompted me
> >> to look into Castor and do some experimenting. It looks very good. Can
> you
> >> share some examples of how you work with SOAP and Castor?
> >>
> >> thanks,
> >>
> >> John
> >>
> >> At 11:54 AM 2/27/01 -0800, you wrote:
> >> >
> >> > I am just wondering if it would be interesting (possible ?) to add new
> >> > Serializers/Deserializers to the SOAP package ?
> >> >
> >> > I have created 2 interesting ones:
> >> >
> >> > - A DOM serializer/deserializer (util tools exist but there are no
> >> > serializers available in the current package)
> >> > - A Castor-XML serializer/deserializer. This one uses the amazing
> >> > Exolab.org Castor package. For people who don't know, this is similar to
> >> > the Javasoft JAXB specification. You can start from an XSD Schema and
> >> > create a full Java framework from it. No need to use DOM or SAX anymore
> >> > ! This serializer/deserializer allows to pass very complex types
> >> > constrained by an XSD Schema and receive on the server side the same
> >> > type.
> >> >
> >> > Any interests ?
> >> >
> >> > Olivier
> >> >
> >> > <file://c:\opt\qualcomm\eudora
> >> > mail\attach\olivier17.vcf>12d7ff0f.jpg<file://c:\opt\qualcomm\eudora
> >> > mail\attach\olivier17.vcf> olivier17.vcf
> >
> >
> ************************************************************************
> John E. Conlon
> jconlon@verticon.com
> tel: (770) 886-5470
> fax: (770) 888-6894
> <http://www.verticon.com/>www.verticon.com
> ************************************************************************
Re: Writing new Serializer/Deserializer
Posted by "John E. Conlon" <jc...@verticon.com>.
At this point I am still educating myself as to the choices for
serializing technologies. I like what I have seen in the Castor, but it
seems that WSDL and IBM's WSTK may also be a fit here.
How would compare WSTK to the Castor approach.
John
At 09:17 AM 3/1/01 -0800, you wrote:
>For example, in the case of implementing a Java client ans a specific service
>(in Java) runiing on the SOAP server, if you are exchanging XML data like the
>UDDI protocol is doing, you don't want to write your
marshaller/unmarshaller for
>each object, so using Castor helps a lot since it is generating everything
for
>you.
>Now you have 2 options:
>
>- Sending the XML yourself through SOAP and change the signature of the
>operation to String or Element
>- Writing your Castor Serializer/Deserializer and having the SOAP server
>marshalling/unmarshalling the XML for you. So your signature will be strongly
>typed, like PurchaseOrder for example. (PurchaseOrder being a Castor
generated
>Class representing an element in your XSD Schema definition).
>
>I have decided to write a CastorSerializer class and a DOM one as well. So
the
>service can use a Java Castor Object and the Client receiving an XML
document as
>a String, in case the caller is not Java. Then if it is Java, you can just
use
>Castor and the unmarshall method to re-initialize the object.
>
>Hope it is clear enough. Looking at the source code of the Date serializer
>helped me a lot. There a still some questions regarding the encodingStyle. I
>have posted a question about it earlier.
>
>Olivier
>
>"John E. Conlon" wrote:
>
>> Your original post and the one concerning business logic validation
>> prompted me
>> to look into Castor and do some experimenting. It looks very good. Can
you
>> share some examples of how you work with SOAP and Castor?
>>
>> thanks,
>>
>> John
>>
>> At 11:54 AM 2/27/01 -0800, you wrote:
>> >
>> > I am just wondering if it would be interesting (possible ?) to add new
>> > Serializers/Deserializers to the SOAP package ?
>> >
>> > I have created 2 interesting ones:
>> >
>> > - A DOM serializer/deserializer (util tools exist but there are no
>> > serializers available in the current package)
>> > - A Castor-XML serializer/deserializer. This one uses the amazing
>> > Exolab.org Castor package. For people who don't know, this is similar to
>> > the Javasoft JAXB specification. You can start from an XSD Schema and
>> > create a full Java framework from it. No need to use DOM or SAX anymore
>> > ! This serializer/deserializer allows to pass very complex types
>> > constrained by an XSD Schema and receive on the server side the same
>> > type.
>> >
>> > Any interests ?
>> >
>> > Olivier
>> >
>> > <file://c:\opt\qualcomm\eudora
>> > mail\attach\olivier17.vcf>12d7ff0f.jpg<file://c:\opt\qualcomm\eudora
>> > mail\attach\olivier17.vcf> olivier17.vcf
>
>
************************************************************************
John E. Conlon
jconlon@verticon.com
tel: (770) 886-5470
fax: (770) 888-6894
<http://www.verticon.com/>www.verticon.com
************************************************************************
Re: Writing new Serializer/Deserializer
Posted by "John E. Conlon" <jc...@verticon.com>.
At this point I am still educating myself as to the choices for
serializing technologies. I like what I have seen in the Castor, but it
seems that WSDL and IBM's WSTK may also be a fit here.
How would compare WSTK to the Castor approach.
John
At 09:17 AM 3/1/01 -0800, you wrote:
>For example, in the case of implementing a Java client ans a specific service
>(in Java) runiing on the SOAP server, if you are exchanging XML data like the
>UDDI protocol is doing, you don't want to write your
marshaller/unmarshaller for
>each object, so using Castor helps a lot since it is generating everything
for
>you.
>Now you have 2 options:
>
>- Sending the XML yourself through SOAP and change the signature of the
>operation to String or Element
>- Writing your Castor Serializer/Deserializer and having the SOAP server
>marshalling/unmarshalling the XML for you. So your signature will be strongly
>typed, like PurchaseOrder for example. (PurchaseOrder being a Castor
generated
>Class representing an element in your XSD Schema definition).
>
>I have decided to write a CastorSerializer class and a DOM one as well. So
the
>service can use a Java Castor Object and the Client receiving an XML
document as
>a String, in case the caller is not Java. Then if it is Java, you can just
use
>Castor and the unmarshall method to re-initialize the object.
>
>Hope it is clear enough. Looking at the source code of the Date serializer
>helped me a lot. There a still some questions regarding the encodingStyle. I
>have posted a question about it earlier.
>
>Olivier
>
>"John E. Conlon" wrote:
>
>> Your original post and the one concerning business logic validation
>> prompted me
>> to look into Castor and do some experimenting. It looks very good. Can
you
>> share some examples of how you work with SOAP and Castor?
>>
>> thanks,
>>
>> John
>>
>> At 11:54 AM 2/27/01 -0800, you wrote:
>> >
>> > I am just wondering if it would be interesting (possible ?) to add new
>> > Serializers/Deserializers to the SOAP package ?
>> >
>> > I have created 2 interesting ones:
>> >
>> > - A DOM serializer/deserializer (util tools exist but there are no
>> > serializers available in the current package)
>> > - A Castor-XML serializer/deserializer. This one uses the amazing
>> > Exolab.org Castor package. For people who don't know, this is similar to
>> > the Javasoft JAXB specification. You can start from an XSD Schema and
>> > create a full Java framework from it. No need to use DOM or SAX anymore
>> > ! This serializer/deserializer allows to pass very complex types
>> > constrained by an XSD Schema and receive on the server side the same
>> > type.
>> >
>> > Any interests ?
>> >
>> > Olivier
>> >
>> > <file://c:\opt\qualcomm\eudora
>> > mail\attach\olivier17.vcf>12d7ff0f.jpg<file://c:\opt\qualcomm\eudora
>> > mail\attach\olivier17.vcf> olivier17.vcf
>
>
************************************************************************
John E. Conlon
jconlon@verticon.com
tel: (770) 886-5470
fax: (770) 888-6894
<http://www.verticon.com/>www.verticon.com
************************************************************************
Re: Writing new Serializer/Deserializer
Posted by Olivier Brand <ol...@intraware.com>.
For example, in the case of implementing a Java client ans a specific service
(in Java) runiing on the SOAP server, if you are exchanging XML data like the
UDDI protocol is doing, you don't want to write your marshaller/unmarshaller for
each object, so using Castor helps a lot since it is generating everything for
you.
Now you have 2 options:
- Sending the XML yourself through SOAP and change the signature of the
operation to String or Element
- Writing your Castor Serializer/Deserializer and having the SOAP server
marshalling/unmarshalling the XML for you. So your signature will be strongly
typed, like PurchaseOrder for example. (PurchaseOrder being a Castor generated
Class representing an element in your XSD Schema definition).
I have decided to write a CastorSerializer class and a DOM one as well. So the
service can use a Java Castor Object and the Client receiving an XML document as
a String, in case the caller is not Java. Then if it is Java, you can just use
Castor and the unmarshall method to re-initialize the object.
Hope it is clear enough. Looking at the source code of the Date serializer
helped me a lot. There a still some questions regarding the encodingStyle. I
have posted a question about it earlier.
Olivier
"John E. Conlon" wrote:
> Your original post and the one concerning business logic validation
> prompted me
> to look into Castor and do some experimenting. It looks very good. Can you
> share some examples of how you work with SOAP and Castor?
>
> thanks,
>
> John
>
> At 11:54 AM 2/27/01 -0800, you wrote:
> >
> > I am just wondering if it would be interesting (possible ?) to add new
> > Serializers/Deserializers to the SOAP package ?
> >
> > I have created 2 interesting ones:
> >
> > - A DOM serializer/deserializer (util tools exist but there are no
> > serializers available in the current package)
> > - A Castor-XML serializer/deserializer. This one uses the amazing
> > Exolab.org Castor package. For people who don't know, this is similar to
> > the Javasoft JAXB specification. You can start from an XSD Schema and
> > create a full Java framework from it. No need to use DOM or SAX anymore
> > ! This serializer/deserializer allows to pass very complex types
> > constrained by an XSD Schema and receive on the server side the same
> > type.
> >
> > Any interests ?
> >
> > Olivier
> >
> > <file://c:\opt\qualcomm\eudora
> > mail\attach\olivier17.vcf>12d7ff0f.jpg<file://c:\opt\qualcomm\eudora
> > mail\attach\olivier17.vcf> olivier17.vcf
Re: Writing new Serializer/Deserializer
Posted by Olivier Brand <ol...@intraware.com>.
For example, in the case of implementing a Java client ans a specific service
(in Java) runiing on the SOAP server, if you are exchanging XML data like the
UDDI protocol is doing, you don't want to write your marshaller/unmarshaller for
each object, so using Castor helps a lot since it is generating everything for
you.
Now you have 2 options:
- Sending the XML yourself through SOAP and change the signature of the
operation to String or Element
- Writing your Castor Serializer/Deserializer and having the SOAP server
marshalling/unmarshalling the XML for you. So your signature will be strongly
typed, like PurchaseOrder for example. (PurchaseOrder being a Castor generated
Class representing an element in your XSD Schema definition).
I have decided to write a CastorSerializer class and a DOM one as well. So the
service can use a Java Castor Object and the Client receiving an XML document as
a String, in case the caller is not Java. Then if it is Java, you can just use
Castor and the unmarshall method to re-initialize the object.
Hope it is clear enough. Looking at the source code of the Date serializer
helped me a lot. There a still some questions regarding the encodingStyle. I
have posted a question about it earlier.
Olivier
"John E. Conlon" wrote:
> Your original post and the one concerning business logic validation
> prompted me
> to look into Castor and do some experimenting. It looks very good. Can you
> share some examples of how you work with SOAP and Castor?
>
> thanks,
>
> John
>
> At 11:54 AM 2/27/01 -0800, you wrote:
> >
> > I am just wondering if it would be interesting (possible ?) to add new
> > Serializers/Deserializers to the SOAP package ?
> >
> > I have created 2 interesting ones:
> >
> > - A DOM serializer/deserializer (util tools exist but there are no
> > serializers available in the current package)
> > - A Castor-XML serializer/deserializer. This one uses the amazing
> > Exolab.org Castor package. For people who don't know, this is similar to
> > the Javasoft JAXB specification. You can start from an XSD Schema and
> > create a full Java framework from it. No need to use DOM or SAX anymore
> > ! This serializer/deserializer allows to pass very complex types
> > constrained by an XSD Schema and receive on the server side the same
> > type.
> >
> > Any interests ?
> >
> > Olivier
> >
> > <file://c:\opt\qualcomm\eudora
> > mail\attach\olivier17.vcf>12d7ff0f.jpg<file://c:\opt\qualcomm\eudora
> > mail\attach\olivier17.vcf> olivier17.vcf
Re: Writing new Serializer/Deserializer
Posted by "John E. Conlon" <jc...@verticon.com>.
Your original post and the one concerning business logic validation
prompted me
to look into Castor and do some experimenting. It looks very good. Can you
share some examples of how you work with SOAP and Castor?
thanks,
John
At 11:54 AM 2/27/01 -0800, you wrote:
>
> I am just wondering if it would be interesting (possible ?) to add new
> Serializers/Deserializers to the SOAP package ?
>
> I have created 2 interesting ones:
>
> - A DOM serializer/deserializer (util tools exist but there are no
> serializers available in the current package)
> - A Castor-XML serializer/deserializer. This one uses the amazing
> Exolab.org Castor package. For people who don't know, this is similar to
> the Javasoft JAXB specification. You can start from an XSD Schema and
> create a full Java framework from it. No need to use DOM or SAX anymore
> ! This serializer/deserializer allows to pass very complex types
> constrained by an XSD Schema and receive on the server side the same
> type.
>
> Any interests ?
>
> Olivier
>
> <file://c:\opt\qualcomm\eudora
> mail\attach\olivier17.vcf>12d7ff0f.jpg<file://c:\opt\qualcomm\eudora
> mail\attach\olivier17.vcf> olivier17.vcf
Re: Writing new Serializer/Deserializer
Posted by "John E. Conlon" <jc...@verticon.com>.
Your original post and the one concerning business logic validation
prompted me
to look into Castor and do some experimenting. It looks very good. Can you
share some examples of how you work with SOAP and Castor?
thanks,
John
At 11:54 AM 2/27/01 -0800, you wrote:
>
> I am just wondering if it would be interesting (possible ?) to add new
> Serializers/Deserializers to the SOAP package ?
>
> I have created 2 interesting ones:
>
> - A DOM serializer/deserializer (util tools exist but there are no
> serializers available in the current package)
> - A Castor-XML serializer/deserializer. This one uses the amazing
> Exolab.org Castor package. For people who don't know, this is similar to
> the Javasoft JAXB specification. You can start from an XSD Schema and
> create a full Java framework from it. No need to use DOM or SAX anymore
> ! This serializer/deserializer allows to pass very complex types
> constrained by an XSD Schema and receive on the server side the same
> type.
>
> Any interests ?
>
> Olivier
>
> <file://c:\opt\qualcomm\eudora
> mail\attach\olivier17.vcf>12d7ff0f.jpg<file://c:\opt\qualcomm\eudora
> mail\attach\olivier17.vcf> olivier17.vcf