Return-Path: Delivered-To: apmail-ws-axis-c-dev-archive@www.apache.org Received: (qmail 20992 invoked from network); 14 Oct 2004 05:38:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 14 Oct 2004 05:38:37 -0000 Received: (qmail 21584 invoked by uid 500); 14 Oct 2004 05:37:58 -0000 Delivered-To: apmail-ws-axis-c-dev-archive@ws.apache.org Received: (qmail 21505 invoked by uid 500); 14 Oct 2004 05:37:58 -0000 Mailing-List: contact axis-c-dev-help@ws.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: List-Id: "Apache AXIS C Developers List" Reply-To: "Apache AXIS C Developers List" Delivered-To: mailing list axis-c-dev@ws.apache.org Received: (qmail 21409 invoked by uid 99); 14 Oct 2004 05:37:56 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=NO_REAL_NAME X-Spam-Check-By: apache.org Received: from [192.18.33.10] (HELO exchange.sun.com) (192.18.33.10) by apache.org (qpsmtpd/0.28) with SMTP; Wed, 13 Oct 2004 22:37:55 -0700 Received: (qmail 28687 invoked from network); 14 Oct 2004 05:39:51 -0000 Received: from localhost (HELO nagoya) (127.0.0.1) by nagoya.betaversion.org with SMTP; 14 Oct 2004 05:39:51 -0000 Message-ID: <746498449.1097732391544.JavaMail.apache@nagoya> Date: Wed, 13 Oct 2004 22:39:51 -0700 (PDT) From: axis-c-dev@ws.apache.org To: axis-c-dev@ws.apache.org Subject: [jira] Commented: (AXISCPP-136) Axis generates wrong response for response messages In-Reply-To: <238658219.1093429404822.JavaMail.apache@nagoya> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N The following comment has been added to this issue: Author: Samisa Abeysinghe Created: Wed, 13 Oct 2004 10:39 PM Body: I used a WSDL with and the generated client code reads: if (AXIS_SUCCESS == m_pCall->invoke()) { if(AXIS_SUCCESS == m_pCall->checkMessage("pingResponse", "uri:weblogscom")) { pReturn = (pingResult*)m_pCall->getCmplxObject((void*) Axis_DeSerialize_pingResult, (void*) Axis_Create_pingResult, (void*) Axis_Delete_pingResult,"pingReturn", 0); } and the generated server code reads: pIWSSZ->createSoapMethod("pingResponse", "uri:weblogscom"); xsd__string v0 = pIWSDZ->getElementAsString("weblogurl",0); xsd__string v1 = pIWSDZ->getElementAsString("weblogname",0); if (AXIS_SUCCESS != (nStatus = pIWSDZ->getStatus())) return nStatus; try { pingResult* ret = pWs->ping(v0,v1); return pIWSSZ->addOutputCmplxParam(ret, (void*)Axis_Serialize_pingResult, (void*)Axis_Delete_pingResult, "pingReturn", Axis_URI_pingResult); } This means both the generated clinet and server are correct. Could this problem be specific to the WSDL file that the reporter has used? (I do not think so) May be the problem is solved with the recent fixes. --------------------------------------------------------------------- View this comment: http://issues.apache.org/jira/browse/AXISCPP-136?page=comments#action_54027 --------------------------------------------------------------------- View the issue: http://issues.apache.org/jira/browse/AXISCPP-136 Here is an overview of the issue: --------------------------------------------------------------------- Key: AXISCPP-136 Summary: Axis generates wrong response for response messages Type: Bug Status: Open Priority: Critical Project: Axis-C++ Components: Serialization/Deserialization Versions: 1.1 Final 1.2 Beta 1.2 Alpha 1.2 Final 1.3 Beta Assignee: Samisa Abeysinghe Reporter: Marcus Tillmanns Created: Wed, 25 Aug 2004 3:22 AM Updated: Wed, 13 Oct 2004 10:39 PM Environment: Windows 2000 Apache 2.50 Description: Axis generates wrong response for well formed WSDL: Instead of naming the return element "resumeJobReturn", Axis generates "JobState", ignoring the correct Name of the part. Works, but only because now both (name and type) have the same name. --------------------------------------------------------------------- JIRA INFORMATION: 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 If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira