You should not use xsd:anyType unless you have no other alternative. It's much better to define a specific type. Axis (or any JAX-RPC implementation, or .NET for that matter) doesn't know how to map an xsd:anyType to a language type, therefore you must supply your own derializer and deserializer.
If you have defined a bean, you can use java2wsdl to convert it to an XML Schema type, although I strongly encourage you to start with schema types and map them to Java types using wsdl2java. Anne On 6/2/05, Christoph Meier <[EMAIL PROTECTED]> wrote: > Thanks a lot for the information, Kiran. > > While reading the WSDL spec I found out that it is possible to use > xsd:anyType in the types definition. I assume this automatically uses > the BeanSerializer and BeanDeserializer? > > Are there any drawbacks involved with anyType (e.g. java specific)? > > Thanks again for the help. > > Chris > > > > Am Donnerstag, den 02.06.2005, 10:37 -0500 schrieb Kiran Kumar: > > Hi, Apache Axis has its own BeanSerializer and BeanDeserializer. However > > Axis supports Castor also. > > > > It is a 2 step process.. > > > > (1) One Define XSD > > (2) Import XSD in your WSDL : Ex- (stockQuote XSD is imported and refer > > that element in port and message tags) > > ===== > > <definitions > > > > targetNamespace="http://w3.ibm.com/schemas/services/2002/11/15/stockquote/wsdl"; > > xmlns="http://schemas.xmlsoap.org/wsdl/"; > > xmlns:tns="http://w3.ibm.com/schemas/services/2002/11/15/stockquote/wsdl"; > > xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"; > > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"; > > xmlns:types="http://w3.ibm.com/schemas/services/2002/11/15/stockquote";> > > <types> > > <xsd:schema elementFormDefault="qualified" > > targetNamespace= > > > > "http://w3.ibm.com/schemas/services/2002/11/15/stockquote/wsdl/importtypes";> > > <import namespace= > > "http://w3.ibm.com/schemas/services/2002/11/15/stockquote"; > > location="StockQuote.xsd" /> > > </xsd:schema> > > </types> > > <message name="getStockQuoteReq"> > > <part name="parameters" element="types:getStockQuote" /> > > </message> > > <message name="getStockQuoteResp"> > > <part name="parameters" element="types:getStockQuoteResponse" /> > > </message> > > <portType name="StockQuotePortType"> > > <operation name="getStockQuote"> > > <input message="tns:getStockQuoteReq" /> > > <output message="tns:getStockQuoteResp" /> > > </operation> > > </portType> > > ...... > > > > (3) Run WSDL2Java, which generates the VOs corresponding to the XSD types.. > > You will have > > to populate these VOs in your service implementation. > > > > PS: > > Refer generated deploy.wsdd which defines the Bean Serializers. > > > > Thanks > > Kiran > > > > ________________________________ > > > > From: Christoph Meier [mailto:[EMAIL PROTECTED] > > Sent: Thu 6/2/2005 10:22 AM > > To: [email protected] > > Subject: BeanSerializer and WSDL > > > > > > > > Hi! > > > > We are developing a document style web service using AXIS. I know it is > > possible to serialize java beans and send them with SOAP. > > > > Is this Axis / Apache SOAP specific? How can I describe such a service > > in a WSDL file (especially <types> part)? > > > > What I have to mention: I don't have AXIS generated stubs at the client > > side because I use a tool for web service orchestration > > (http://www.jopera.org), that has it's own SOAP engine and uses only the > > WSDL file. > > > > Is it only possible if I define the bean's XML schema in the WSDL file? > > > > Thanks a lot for your help. I don't find much information on this topic > > in the web. > > > > > > Chris > > > > > > > > > > ------------------------------------------------ > > > > This e-mail, and any attachments thereto, is confidential and is intended > > only for the individual(s) named. If you are not the intended recipient, > > please let us know by e-mail reply and delete it from your system; do not > > copy/save this e-mail or disclose its contents to anyone. E-mail > > transmissions cannot be guaranteed to be secure or error-free as the > > transmission could be interrupted, corrupted, lost, destroyed, altered, > > arrive late or contain viruses. ObjectWave does not accept liability for > > any errors or omissions in the contents of this e-mail which arise as a > > result of e-mail transmission. The views expressed in this e-mail do not > > necessarily reflect those of ObjectWave or its affiliates. > > > > ------------------------------------------------ > > > > > >
