Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 55103 invoked from network); 29 Sep 2003 16:08:22 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 29 Sep 2003 16:08:22 -0000 Received: (qmail 28921 invoked by uid 500); 29 Sep 2003 16:08:01 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 28891 invoked by uid 500); 29 Sep 2003 16:08:01 -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: Delivered-To: mailing list axis-user@ws.apache.org Delivered-To: moderator for axis-user@ws.apache.org Received: (qmail 20428 invoked from network); 29 Sep 2003 16:00:05 -0000 Message-ID: <20030929160007.93027.qmail@web20711.mail.yahoo.com> Date: Mon, 29 Sep 2003 09:00:07 -0700 (PDT) From: Subject: [Wrapped/Literal] No Deserializer defined for array of xsd:string To: axis-user@ws.apache.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hi I am using Axis 1.1 to call a wrapped service. I have a simple Java class public class Test { �public TestResponse callMethod( String method, String[] params ) �{ ��return( null ); �} } The wsdl for this Java class was produced using org.apache.axis.wsdl.Java2WSDL, the options --style WRAPPED --use LITERAL specified. The client stub and server impl were produced using org.apache.axis.wsdl.WSDL2Java. When the service is called the following SOAP request and AXIS fault response are produced :- � �� test �� �� soapenv:Server.userException �� org.xml.sax.SAXException: No deserializer defined for array type {http://www.w3.org/2001/XMLSchema}string �� Firstly, I am a little confused why when --use LITERAL is specified to Java2WSDL that the string array is still SOAP encoded ?. I have seem some debate on this issue recently. � Secondly, the problem I am seeing appears to be caused by the attribute xsi:type="Array" on the element. The value "Array" is not indicated to be in the http://schemas.xmlsoap.org/soap/encoding/" namespace using the defined "soapenc" prefix. On further investigation this may be caused by a what appears to be a bug in the class org.apache.axis.utils.NStack. The stack believes that "http://schemas.xmlsoap.org/soap/encoding/" namespace is the default namespace and hence does not require a prefix. This only occurs at the point when this attribute is serialized. � I would appreciate your thoughts/advice, Is this a bug ? am I doing something wrong ? � Thanks Steve __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com