axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 18287] - Error in serialization of xsd:boolean fields
Date Sat, 29 Nov 2003 03:01:45 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18287>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18287

Error in serialization of xsd:boolean fields

gdaniels@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|REOPENED                    |RESOLVED
         Resolution|                            |FIXED



------- Additional Comments From gdaniels@apache.org  2003-11-29 03:01 -------
OK, a couple of points here.

1) The answer to "how was this passing the TCK" is that soapenc:int is a 
subtype of xsd:int.  So any system which knows about soapenc:int should accept 
one of those as an xsd:int.  The problem is that SOAP processors are not 
required to know about soapenc:int, so doing this change transparently is a 
bad idea.

2) On a related note, I just essentially removed the getNillableQName() calls 
because we just shouldn't be altering the schema types like that.  I haven't 
looked closely yet, but I'm guessing we do a better job at mapping 
nillable/minOccurs="0" types to wrapper classes now, since nothing broke in 
the test suite.  Or do we not have a test for that?

3) This is fixed now. :)

Mime
View raw message