[prev in list] [next in list] [prev in thread] [next in thread] 

List:       axis-dev
Subject:    [jira] Updated: (AXIS-1525) xsd:group behavior is wrong
From:       "Michael Thome (JIRA)" <axis-dev () ws ! apache ! org>
Date:       2005-05-31 19:02:53
Message-ID: 1975174127.1117566173286.JavaMail.jira () ajax ! apache ! org
[Download RAW message or body]

     [ http://issues.apache.org/jira/browse/AXIS-1525?page=all ]

Michael Thome updated AXIS-1525:
--------------------------------

    Attachment: another.wsdl

In the spirit of the previous example, here is a sample wsdl file.  Compare the code \
generated for OneType with AnotherType

> xsd:group behavior is wrong
> ---------------------------
> 
> Key: AXIS-1525
> URL: http://issues.apache.org/jira/browse/AXIS-1525
> Project: Axis
> Type: Bug
> Components: Serialization/Deserialization
> Versions: 1.2 Beta
> Reporter: Steve Green
> Fix For: 1.2.1
> Attachments: 1525.diff, SomeType.java, another.wsdl, group.patch, groupgen.patch, \
> sample.wsdl, test.wsdl.groups.tar 
> 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:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


[prev in list] [next in list] [prev in thread] [next in thread]