Dang! Interop tests! I KNEW I forgot to check something! I'm on it...
Another question for y'all. JAX-RPC changed the mapping of xsd:dateTime
from java.util.Date to java.util.Calendar. When I changed it, I left the
mapping of xsd:date to java.util.Date. Now I'm beggining to think I
shouldn't have for two reasons:
- the Java->XML mapping - java.util.Date->xsd:date - is misleading. It
makes one think that you can pass a Date object across the wire, but all
that really goes across is the date portion of the Date object (ie.,
"yyyy-MM-dd"), the time stuff is ignored.
- we don't map xsd:time. But if folks see that we map xsd:dateTime and
xsd:date, they'll expect xsd:time as well. And how would we map xsd:time?
We can't use java.util.Date for BOTH xsd:date and xsd:time because that
would break roundtripping.
So what do folks think? Should I get rid of the xsd:date mapping? It's
not part of JAX-RPC and I don't believe users have complained that we don't
have it.
Russell Butek
[EMAIL PROTECTED]
Sam Ruby/Raleigh/IBM@IBMUS on 03/31/2002 06:21:52 PM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Re: cvs commit: xml-axis/java/test/wsdl/types
ComprehensiveTypes.wsdl VerifyTestCase.java
FYI: all of the echo interop tests (except TCLSOAP) are failing now for
echoDate.
http://www.apache.org/~rubys/ApacheClientInterop.html
- Sam Ruby
