One other thing I forgot to mention is that in some cases you may find that you do not
need to write a serializer. For many of my value objects the BeanSerializer or
SimpleSerializer did just fine, it was only the deserialization that required me to
write code.
The WSDD files need somethin
Is there a good reference you can point me to for hand-creation of WSDL
and WSDD that would include use of non-bean objects? I think that lack
of knowledge is part of my stumbling.
My knowledge is based mainly on "Building Web Services with Java" by Steve Graham et
al, published by SAMS. The
> That's my experience - Java2WSDL would tend to generate a file
> without most of the section, which was a pain, but
> work-around-able. In my case these objects tended to be read-only,
> without a default constructor, and with getX methods but no
> corresponding setX methods.
This is very simil
So for non-bean
serialization/deserialization I can't use Java2WSDL and WSDL2Java?
That's my experience - Java2WSDL would tend to generate a file without most of the
section, which was a pain, but work-around-able. In my case these objects
tended to be read-only, without a default constructo
Thanks I'll look into this more. So for non-bean
serialization/deserialization I can't use Java2WSDL and WSDL2Java?
-- Jason
On Wednesday 21 January 2004 14:08, [EMAIL PROTECTED] wrote:
> Hi Jason,
>
> What you need to do is define your own serializer/deserializer that
> knows how to convert yo
Hi Jason,
What you need to do is define your own serializer/deserializer that knows
how to convert your objects from/to XML. You do this implementing the
org.apache.axis.encoding.Serializer and
org.apache.axis.encoding.Deserializer interfaces. If you take a look at
the source for org.apach.axis.
