Actually the way it works is that when you use Java2WSDL on your service bean, and WSDL2Java to create the client classes from the generated WSDL, it will set up the serialization/deserialization for you. That is if you have correctly constructed the service bean to utilize the class for the bean you want to return. The Java2WSDL will use the bean classes to add the type definition to the WSDL for the bean that will be passed back to the client class. If you use the user guide examples, check out Example 5. I use Eclipse 3.1.1 with the WTP 0.7 plugin, which makes it very easy to do all this. In this case of Example 5, once you have used WSDL2Java to create the client classes, you will notice that it has created a new version of the Order bean, and it has the deserializer code added to it, down towards the bottom.
Also check out this page, it may help you:
After I got this one working, I modified it to return an array of beans, which was fairly easy.
HTH 8)
Jim
Hans Rupp <[EMAIL PROTECTED]> wrote:
Hans Rupp <[EMAIL PROTECTED]> wrote:
Hello,
i have a question about the (Bean)Desializer-classes from Axis. I have
created the client-classes
for a webservice using wsdl2java. There is a class Order.java with methods
to get a Serializer/Deserializer
for this class. How can i use the Deserializer returned by this method to
transform an XML-file (or a string
containing the xml) into an Object of type order or is this impossible?
The Api-doc und the axis-user-guide.html doesn't really help me further.
Any suggestions?
Thanks
Hans
