Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 54936 invoked from network); 8 Feb 2006 22:23:02 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 8 Feb 2006 22:23:02 -0000 Received: (qmail 83096 invoked by uid 500); 8 Feb 2006 22:22:48 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 82884 invoked by uid 500); 8 Feb 2006 22:22:47 -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 82789 invoked by uid 99); 8 Feb 2006 22:22:46 -0000 X-ASF-Spam-Status: No, hits=1.3 required=10.0 tests=SPF_FAIL 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, 08 Feb 2006 14:22:46 -0800 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 0626A126 for ; Wed, 8 Feb 2006 23:22:25 +0100 (CET) Message-ID: <2127504170.1139437345017.JavaMail.jira@ajax.apache.org> Date: Wed, 8 Feb 2006 23:22:25 +0100 (CET) From: "Tom Jordahl (JIRA)" To: axis-dev@ws.apache.org Subject: [jira] Commented: (AXIS-2386) Java2WSDL changes type double array into a single double. In-Reply-To: <950412508.1138394562514.JavaMail.jira@ajax.apache.org> 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/AXIS-2386?page=comments#action_12365642 ] Tom Jordahl commented on AXIS-2386: ----------------------------------- The code is the same for ?WSDL generation and Java2WSDL. So if one works and the other doesn't, it would be interesting to know why. Configuration? Why is this bug appearing now? Is there a test case in the Axis test suite? Did ths ever work (in 1.1 or 1.2)? In summary, you will probably have to do more digging and possibly provide a patch yourself. > Java2WSDL changes type double array into a single double. > --------------------------------------------------------- > > Key: AXIS-2386 > URL: http://issues.apache.org/jira/browse/AXIS-2386 > Project: Apache Axis > Type: Bug > Components: WSDL processing > Versions: 1.2.1, 1.3 > Environment: Linux 2.4.26, java version "1.5.0_04", Tomcat 5.5 > Reporter: Eric Webster > Priority: Minor > Attachments: DataSet.wsdl, IncorrectDataSet.wsdl > > Java2WSDL changes type double array into a single double. > This happens when you run Java2WSDL manually on the command line or when a wsdl file is generated from a service_name?wsdl url. > Currently to fix this I just manually edit the generated WSDL file and distrobute that. > The Java code originally came from a hand made WSDL file. WSDL2Java was used to generate the Java code. The section that is affected by this problem is the 'ValueVector' complexType which contains and element 'values' which is an array of doubles. After converting to Java and then back to WSDL 'values' becomes a single double. > Here is the original WSDL file. > > targetNamespace="dataset.odin.cirg.washington.edu" > xmlns:apachesoap="http://xml.apache.org/xml-soap" > xmlns:impl="dataset.odin.cirg.washington.edu" > xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" > xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" > xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" > xmlns:xsd="http://www.w3.org/2001/XMLSchema"> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Here is what 'ValueVector' turns into after running WSDL2Java (which creates correct java code) and then Java2WSDL. > > > > > > > > > > > -- 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