It appears that the timestamp added to the SOAP header by the WSE 3.0 (and 
WSE 2.0) modules only has 1 second resolution.  We use these enhancements to 
interact with a Web Service of our own creation which tries to minimize 
"replay attacks" by checking the timestamp in the SOAP headers.  Our Java 
client, which we use on MACs, correctly provides timestamps with millisecond 
resolution, but the Windows client requests always come in with timestamps 
that show .000, that is no milliseconds.

Is there anyway to get millisecond resolution in the timestamp field, or 
alternatively anyway from client code to set this field ?

-- 
Joel Goldberger
Flagstaff, AZ