Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 45017 invoked from network); 4 Aug 2005 06:28:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 4 Aug 2005 06:28:00 -0000 Received: (qmail 73724 invoked by uid 500); 4 Aug 2005 06:27:54 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 73530 invoked by uid 500); 4 Aug 2005 06:27:52 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 73517 invoked by uid 99); 4 Aug 2005 06:27:52 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Aug 2005 23:27:40 -0700 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 8138FE4 for ; Thu, 4 Aug 2005 08:27:37 +0200 (CEST) Message-ID: <1739695480.1123136857527.JavaMail.jira@ajax.apache.org> Date: Thu, 4 Aug 2005 08:27:37 +0200 (CEST) From: "Chathura Herath (JIRA)" To: axis-dev@ws.apache.org Subject: [jira] Commented: (AXIS2-112) Doclitparams Interoperability Test failed Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/AXIS2-112?page=comments#action_12317590 ] Chathura Herath commented on AXIS2-112: --------------------------------------- THe actual problem is with the fact that we go by the WSDL 2.0 component model and there is no notion of part or messages in that. This is being handled in the following manner. For a particular operation op1 if there are two messages inmsg and outmsg. If the messages have only one part in the time of building the wom the wom builder will look up the message and get the part from it and get the element that the part refers to and that element will go as the qname of the message reference. This enables us to by pass the message construct and to do a successful lossless migration to WSDL 2.0 component model. If a given message, say inmsg has two or more parts say inmsgpart1 and inmsgpart2 then the message reference of the wom cannot refer to a qname directly. In this case what happens is that the wom builder will create a new wrapper element (name of which will be the multipart message name) and the each qname refered by the individual parts will be included in this new complex (wrapper schema) type as complex content and it is to this newly created element that the message reference will be refering to. > Doclitparams Interoperability Test failed > ----------------------------------------- > > Key: AXIS2-112 > URL: http://issues.apache.org/jira/browse/AXIS2-112 > Project: Apache Axis 2.0 (Axis2) > Type: Bug > Versions: 0.9 > Environment: Windows XP > j2sdk1.4.2_01 > Reporter: Nadana Gunaratna > Assignee: Chathura Herath > > Service Info: > WSDL Location:http://soapinterop.java.sun.com/round3/groupd/doclitparams?WSDL > Service Location: http://soapinterop.java.sun.com:80/round3/groupd/doclitparams > For more Information: > http://soapinterop.java.sun.com > The Request SOAP was produced using the generated stubs (using WSDL2Java). A SOAP fault was received as the response. > Request SOAP Message as displayed in theTCP monitor: > POST /round3/groupd/doclitparams HTTP/1.1 > Content-Type: text/xml; charset=utf-8 > Accept: application/soap+xml, application/dime, multipart/related, text/* > Host: soapinterop.java.sun.com > Cache-Control: no-cache > Pragma: no-cache > Content-Length: 236 > SOAPAction: "http://soapinterop.org/" > > > > > hi > > > Response SOAP Message: > HTTP/1.1 500 Internal Server Error > SOAPAction: "" > Content-Type: text/xml; charset="utf-8" > Transfer-Encoding: chunked > Date: Sat, 30 Jul 2005 04:41:46 GMT > Server: Apache Coyote/1.0 > > 21e > > > > > env:Client > caught exception while handling request: unexpected element name: expected=param0, actual={http://soapinterop.org/xsd}param0 > > > > 0 > > Then the SOAP message was modified as follows, i.e. the first child of the body was pre-fixed with the local name of the namespace, and resent from the TCP Monitor, Request SOAP Message accepted as correct and received Response as follows. > Request SOAP Message: > POST /round3/groupd/doclitparams HTTP/1.1 > Content-Type: text/xml; charset=utf-8 > Accept: application/soap+xml, application/dime, multipart/related, text/* > Host: soapinterop.java.sun.com > Cache-Control: no-cache > Pragma: no-cache > Content-Length: 590 > SOAPAction: "http://soapinterop.org/" > > > > > hi > > > > Response SOAP Message: > HTTP/1.1 200 OK > SOAPAction: "" > Content-Type: text/xml; charset="utf-8" > Transfer-Encoding: chunked > Date: Sat, 30 Jul 2005 06:29:45 GMT > Server: Apache Coyote/1.0 > > 193 > > > > > hi > > > > 0 > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira