Hi All, Do you know if its possible to deal with rampart - at the proxy configuration level - to disable milliseconds precision in timestamp through the Synapse configuration?
Consuming .Net services with milliseconds doesn't work in my specific case and I had to apply the patch in attachment to disable the milliseconds. This patch is far to be perfect, because I change the global configuration instead of change the configuration at the message context. This patch allows to define the timestamp precision settings through the ramport config xml fragment enclosed in the policy file: <ramp:RampartConfig xmlns:ramp="http://ws.apache.org/rampart/policy";> <ramp:timestampPrecisionInMilliseconds>false</ramp:timestampPrecisionInMilliseconds> </ramp:RampartConfig> If one of synapse commiters could push forward to the rampart commiters. They could improve and apply the patch to the trunk of rampart and consequently enabling such feature in Synapse. Regards, Alexandre http://www.nabble.com/file/p16718940/rampart-timestamp-precision-in-milliseconds.patch rampart-timestamp-precision-in-milliseconds.patch -- View this message in context: http://www.nabble.com/Timestamp-Precision-In-Milliseconds-Configuration-At-Proxy-Level-tp16718940p16718940.html Sent from the Synapse - User mailing list archive at Nabble.com.
