I think I read somewhere that nested complextypes are not possible in wsdl, but I'm not sure. If you succeed I would be happy to hear your solution. currently it is not important for me, but I see the same issues ahead later this year. Roger Stoffers Vodafone
-----Original Message----- From: Wierenga, R. - SPLXE [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 11, 2004 3:27 PM To: '[EMAIL PROTECTED]' Subject: axis 1.1 and jaxb Hi ! I'm trying to use jaxb as the (de)serialization mechanism for the provision of a document/literal style webservice. Has anyone succeeded in implementing this? I'm curious to know which steps i need to take. Steps i took so far are: * created a wsdl file including the schema for my complextypes * used axis wsdl2java tool to generate the skeleton, implementation and beans sources * created a custom JAXB serializer based on Castor serializer example * modified wsdd to use the new JAXB serializer for each compleyType and element defined in the schema * deployed stuff using adminclient * tested results using WSAD 5.1 Webservice explorer Problems which i encountered: * A call to the webservice results in a Soap fault (java.lang.reflect.InvocationTargetException) * The wsdl file generated by Axis after deployment is invalid, it does not contain the complexType definitions which were defined in the original wsdl. How could this happen? When I leave out the type mappings in my deploy.wsdd and redeploy it produces a valid wsdl file...strange. Kinds regards, Robin Wierenga ********************************************************************** For information, services and offers, please visit our web site: http://www.klm.com. This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **********************************************************************
