In beta2 java.util.Date incorrectly maps to soap date, in beta3 it maps to dateTime.
Although it should not be an issue for you now, Calendar is not a singleton and should work fine in beta2. ----- Original Message ----- From: "Stickley, Jim" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, July 13, 2002 1:16 AM Subject: SOAP to Java type mappings... > Can anyone point me to the documentation that defines how java types are > mapped to SOAP types? I would like to find the Java time that maps a SOAP > dateTime type. If this documentation exists, please add it to the User > Guide, since this is critical to building services. > > >From inspecting the Axis code it appears that the java.util.Calendar type > maps to the SOAP dateTime type, but this is really not a very good mapping > as the Calendar type is a singleton. Thus, if you have to build an SOAP > interface that moves more than one Calendar object, then you end up with one > Calendar instance attempting to capture all three date values, so the > receiving end of the SOAP message will see the same value for all three > dateTime objects. > > If what I am say is true, then I would recommend the following mappings: > > Java type SOAP Type > -------------- --------- > java.util.Date dateTime > <no type> date > > The reason I recommend this is that the SOAP date type is not as useful as > the SOAP dateTime type. And, those that do not need the Time dimension can > just ignore it. > > Jim Stickley > Birch Telecom > (816) 300-6743 > [EMAIL PROTECTED] > > >
