You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Tom Jordahl <to...@macromedia.com> on 2003/07/07 21:32:07 UTC
RE: JAX-RPC TCK - Axis 1.1
TCK isn't a magic test suite. It is certainly possible that Axis was generating something wrong and still passing the test suite.
--
Tom Jordahl
Macromedia Server Development
-----Original Message-----
From: Michael Ryan [mailto:Michael.Ryan@stellent.com]
Sent: Monday, June 30, 2003 1:29 PM
To: axis-dev@ws.apache.org
Subject: RE: JAX-RPC TCK - Axis 1.1
Hi guys-
This bug hasn't been touched in a while, so I was wondering if
anyone has looked at it recently.
Just curious, but if this fix broke the TCK, how was code that
is generated incorrectly passing the TCK? If the generated SOAP doesn't
match the WSDL, how is that getting through the TCK?
Thanks for the help,
Mike Ryan
-----Original Message-----
From: Tom Jordahl [mailto:tomj@macromedia.com]
Sent: Monday, April 07, 2003 3:17 PM
To: 'axis-dev@ws.apache.org'
Subject: JAX-RPC TCK - Axis 1.1
Continuing in our discussion of how "reproducible" the TCK results are,
this bug fix in 1.1 actually broke several TCK tests.
Upon having our testers 'start from scratch' and re-run the test, it
turns out we DO have failures. Don't blame me; I just pass along what
they tell me. :-(
--
Tom Jordahl
Macromedia Server Development
-----Original Message-----
From: bugzilla@apache.org [mailto:bugzilla@apache.org]
Sent: Monday, April 07, 2003 4:13 PM
To: axis-dev@ws.apache.org
Subject: DO NOT REPLY [Bug 18287] - Error in serialization of
xsd:boolean fields
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
tomj@macromedia.com changed:
What |Removed |Added
------------------------------------------------------------------------
----
Status|RESOLVED |REOPENED
Resolution|FIXED |
------- Additional Comments From tomj@macromedia.com 2003-04-07 20:13
------- Dims, This change broke things. WSDL2Java now no longer converts
<element name="nilint" type="xsd:int" nillable="true"/>
To an Integer, but rather an int.
We need to solve this another way and correctly map nillable=true xsd
types to
their Java wrappers.