Ruchith Fernando wrote: > IIRC this was originally added to support older ws-sec specs. The only > use of this I can see right now is to be able to dynamically configure > wss4j to disable strict timestamp handling. (See > WSSConfig#timeStampStrict and TimestampProcessor#handleTimestamp()). > Not sure whether there's anyone who is using this. > > I'm 0 on removing this. > AFAIK some projects used this to disable timestamp handling (.Net didn't or doesn't support the millisecond feature). This can be set using a parameter. Otherweise I don't see any further usage anymore.
Regards, Werner > Thanks, > Ruchith > > On 4/13/07, Fred Dushin <[EMAIL PROTECTED]> wrote: >> Is there any reason for this? I'm really puzzled as to why there is >> a static mutator on this class, and my the (non-static) process >> results operations are using statically configured data. >> >> Anyone care if I remove this (in a patch)? The sources compile and >> the tests pass without it. >> >> Thanks, >> -Fred >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
