I also see in the "known issues" section of JWSDP 1.4/1.5 the following:
"JAX-RPC cannot fully round-trip Calendar objects that have a time zone that
includes a GMT offset with non-zero seconds. For example, a GMT time zone
offset of GMT-11:00:04 cannot be round tripped because the XML schema
dateTime format does not allow for the specification of seconds in the GMT
offset."
I'm not sure I quite understand the above statement completely. If a JAX-RPC
client is passing a date as a Calendar (from Calendar.getInstance(), for
example), would there ever be a problem converting that to an appropriate
dateTime value in the SOAP message that is sent over the wire for a static
stub?
-- Ryan
-----Original Message-----
From: Ryan LeCompte [mailto:ryan.lecompte_at_pangonetworks.com]
Sent: Friday, November 12, 2004 2:11 PM
To: 'users_at_jax-rpc.dev.java.net'
Subject: RE: JAXRPC 1.1.2_01 releases as part of JWSDP 1.5
Doug,
Congratulations on the JWSDP 1.5 release. The "What's New" section of the
JAX-RPC release notes for JWSDP 1.5 and JWSDP 1.4 appear to be identical
(support for WS-I Basic Profile 1.1, support for WS-I Attachment Profile
1.0, and support for WS-I Simple SOAP Binding Profile 1.0). Does the JAX-RPC
release that comes with JWSDP 1.5 provide any signifcant new features, or
mainly bug fixes?
Regards,
-- Ryan
-----Original Message-----
From: Doug Kohlert [mailto:Doug.Kohlert_at_Sun.COM]
Sent: Friday, November 12, 2004 2:04 PM
To: users_at_jax-rpc.dev.java.net
Subject: JAXRPC 1.1.2_01 releases as part of JWSDP 1.5
For more information please see:
https://jax-rpc.dev.java.net/servlets/NewsItemView?newsItemID=1465
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_jax-rpc.dev.java.net
For additional commands, e-mail: users-help_at_jax-rpc.dev.java.net