Before I dive into any code changes, has anyone else had problems with the
DateSerialzier? I have a SOAP method that has a Date as one of the params.
When it gets two simultaneous calls the dates seem to be wrong, not the same
as what was passed to call.invoke(). As far as I can tell good dates are
going in and bad dates are getting passed into my Soap method by the rpc
router.
I peeked at DateSerializer and it uses two SimpleDateFormat objects, which
it creates in the constructor and stores in member variables. No use of
these SimpleDateFormat objects use any synchronization. If the rpc router
just creates a single DateSerializer and reuses it then it seems to me this
would be a problem. Can anyone verify?
Thanks
Rick
