Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 56410 invoked from network); 31 May 2006 15:02:52 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 31 May 2006 15:02:52 -0000 Received: (qmail 69953 invoked by uid 500); 31 May 2006 15:02:42 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 69939 invoked by uid 500); 31 May 2006 15:02:42 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 69928 invoked by uid 99); 31 May 2006 15:02:42 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 31 May 2006 08:02:42 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,RCVD_IN_BL_SPAMCOP_NET,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of xjchen001@gmail.com designates 64.233.182.191 as permitted sender) Received: from [64.233.182.191] (HELO nf-out-0910.google.com) (64.233.182.191) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 31 May 2006 08:02:41 -0700 Received: by nf-out-0910.google.com with SMTP id g2so76034nfe for ; Wed, 31 May 2006 08:02:19 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=gMe/ntoVLU5qEGTmGWkmrnXep7EOGC8OVoDIoP6jtLHjnflrVkTPDxXq7XeiGD8YPxuS7VqnX4Hr18kQ/ubQfXUlVMHXAkkTgfAz6jlKFdIc+2SqZKYB9maJcnljitj+8DHXD4FY1ibF5rmRYW/cu1Dbau7xaKxkJqBkimFAj/o= Received: by 10.49.54.2 with SMTP id g2mr376424nfk; Wed, 31 May 2006 08:02:19 -0700 (PDT) Received: by 10.49.9.20 with HTTP; Wed, 31 May 2006 08:02:19 -0700 (PDT) Message-ID: <84f31d220605310802k676513c6vca96c9ded919667d@mail.gmail.com> Date: Wed, 31 May 2006 23:02:19 +0800 From: "Xinjun Chen" To: axis-user@ws.apache.org Subject: Re: [Axis 1.4] No deserializer for anyType In-Reply-To: <4611715.post@talk.nabble.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_17535_194690.1149087739613" References: <4608778.post@talk.nabble.com> <4611715.post@talk.nabble.com> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_17535_194690.1149087739613 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Adnene, The following two articles may help you to understand your problem. To put it simple, the service style matters significantly! First one is Anne's explanation on RPC style and document style. http://searchwebservices.techtarget.com/ateQuestionNResponse/0,289625,sid26_cid494324_tax289201,00.html The second one is from IBM developerworks. It describes the service style and encoding very clearly. http://www-128.ibm.com/developerworks/webservices/library/ws-whichwsdl/ For your problem, when you are using RPC style, the anyType works because in your request message, the actual xsd type is specify and attached in the request message. The server side relies on your request message (the acutal xsd type, say xsd:string, not xsd:anyType) to deserialize your XML into java object. However, in document style, the deserialization of request message is based on a schema. This is a contract agreed upon between the service client and the service provider. The representation of this agreement is the // in the service's WSDL file. When you use RPC style, the server side try to find a deserializer for xsd:string or other type specified in the request message to deserialize your request message. When you switch from RPC style to Document style, the server side will try to find a deserializer for xsd:anyType from typemapping registry to deserialize the request message. However, you didn't specify any serializer/deserializer for xsd:anyType, that's why you get that Exception. Therefore, Anne suggest you use DOM object, say org.w3c.Document. Hope this clear your doubts. Regards, Xinjun On 5/29/06, Adnene wrote: > > > Thank you Anne For your quick answer, > > Since I am new with Axis and SOAP, do you have any reference or > documentation to point me to, so I can find out the way to tell Axis how > to > process this information? > An example would of a great help for me. > > Thank you again for precious help, > > Adnene > > -- > View this message in context: > http://www.nabble.com/-Axis+1.4-+No+deserializer+for+anyType-t1698308.html#a4611715 > Sent from the Axis - User forum at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org > For additional commands, e-mail: axis-user-help@ws.apache.org > > ------=_Part_17535_194690.1149087739613 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
Adnene,
 
The following two articles may help you to understand your problem. To put it simple, the service style matters significantly!
First one is Anne's explanation on RPC style and document style.
 
The second one is from IBM developerworks. It describes the service style and encoding very clearly.
For your problem, when you are using RPC style, the anyType works because in your request message, the actual xsd type is specify and attached in the request message. The server side relies on your request message (the acutal xsd type, say xsd:string, not xsd:anyType) to deserialize your XML into java object. However, in document style, the deserialization of request message is based on a schema. This is a contract agreed upon between the service client and the service provider. The representation of this agreement is the <definitions>/<types>/<schema> in the service's WSDL file.
When you use RPC style, the server side try to find a deserializer for xsd:string or other type specified in the request message to deserialize your request message. When you switch from RPC style to Document style, the server side will try to find a deserializer for xsd:anyType from typemapping registry to deserialize the request message. However, you didn't specify any serializer/deserializer for xsd:anyType, that's why you get that Exception.
 
Therefore, Anne suggest you use DOM object, say org.w3c.Document.
 
Hope this clear your doubts.
 
 
Regards,
Xinjun

 
On 5/29/06, Adnene <abenabdallah@infovista.com> wrote:

Thank you Anne For your quick answer,

Since I am new with Axis and SOAP, do you have any reference or
documentation to point me to, so I can find out the way to tell Axis how to
process this information?
An example would of a great help for me.

Thank you again for precious help,

Adnene

--
View this message in context: http://www.nabble.com/-Axis+1.4-+No+deserializer+for+anyType-t1698308.html#a4611715
Sent from the Axis - User forum at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org


------=_Part_17535_194690.1149087739613--