axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Updated: (AXIS-1525) xsd:group behavior is wrong
Date Thu, 21 Oct 2004 15:12:14 GMT
The following issue has been updated:

    Updater: Steve Green (
       Date: Thu, 21 Oct 2004 8:11 AM
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.
             Attachment changed to group.patch
For a full history of the issue, see:

View the issue:

Here is an overview of the issue:
        Key: AXIS-1525
    Summary: xsd:group behavior is wrong
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Axis
             1.2 Beta

   Reporter: Steve Green

    Created: Mon, 23 Aug 2004 3:25 PM
    Updated: Thu, 21 Oct 2004 8:11 AM

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.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message