Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 8046 invoked from network); 21 Oct 2004 15:10:21 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 21 Oct 2004 15:10:21 -0000 Received: (qmail 14166 invoked by uid 500); 21 Oct 2004 15:10:14 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 14023 invoked by uid 500); 21 Oct 2004 15:10:12 -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: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 14012 invoked by uid 99); 21 Oct 2004 15:10:12 -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; Thu, 21 Oct 2004 08:10:12 -0700 Received: (qmail 18355 invoked from network); 21 Oct 2004 15:12:14 -0000 Received: from localhost (HELO nagoya) (127.0.0.1) by nagoya.betaversion.org with SMTP; 21 Oct 2004 15:12:14 -0000 Message-ID: <1681589600.1098371534691.JavaMail.apache@nagoya> Date: Thu, 21 Oct 2004 08:12:14 -0700 (PDT) From: axis-dev@ws.apache.org To: axis-dev@ws.apache.org Subject: [jira] Updated: (AXIS-1525) xsd:group behavior is wrong In-Reply-To: <747724829.1093299920090.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 issue has been updated: Updater: Steve Green (mailto:steve.green@epok.net) Date: Thu, 21 Oct 2004 8:11 AM Comment: Attached is a patch that adds group support for WSDL2java. The approach was to treat a group reference like as if it was a macro inclusion. That is, a group reference results in putting the group member fields directly into the referencing class. Please note that my understaning of WSDL2java may not be complete enough to guarantee that this patch does 100% of what is needed to really fix this problem. Changes: Attachment changed to group.patch --------------------------------------------------------------------- For a full history of the issue, see: http://issues.apache.org/jira/browse/AXIS-1525?page=history --------------------------------------------------------------------- View the issue: http://issues.apache.org/jira/browse/AXIS-1525 Here is an overview of the issue: --------------------------------------------------------------------- Key: AXIS-1525 Summary: xsd:group behavior is wrong Type: Bug Status: Unassigned Priority: Major Project: Axis Components: Serialization/Deserialization Versions: 1.2 Beta Assignee: Reporter: Steve Green Created: Mon, 23 Aug 2004 3:25 PM Updated: Thu, 21 Oct 2004 8:11 AM Description: WSDL2Java generates separate types for groups, and objects that reference groups end up with a children object. The problem is that serialization of that object should not show the group in XML. The elements of the group should appear on the wire as if they were elements of the referencing object. It seems that the problem might be fixable by changing the way in which WSDL2Java generates classes with groups. The bean writer could recurse in to groups and treat the elements as elements of the object being written. This might create problems when trying to properly handle xsd attributes like minOccurs=0, etc.. that appear on the group reference. Another possible solution would be to add some info to the type description so that the serialization could could recognize a group reference and do the right thing. The same would need to be true of the deserializer. This fix involves a change to the code generator as well as changes to the Axis engine. N O T E: I am interested in supplying a fix for this problem. Please comments on this issue so that I chose the method that best fits the design goals of the Axis developers. --------------------------------------------------------------------- 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