Hi Karthik, My workaround was the same as I posted above. In short, it was:
1. Create an interceptor that will save the time when the message is first received. 2. Override the default timestamp validator with a custom one. This custom one will use the time saved for comparison with the message timestamp rather than using the current time. 3. Register both the interceptor and the timestamp in cxf-servlet.xml Here is the code that I wrote for the interceptor: https://github.com/CONNECT-Solution/CONNECT/blob/4.0.0/Product/Production/Common/CONNECTCoreLib/src/main/java/gov/hhs/fha/nhinc/callback/cxf/largefile/TimestampInterceptor.java For the timestamp validator: https://github.com/CONNECT-Solution/CONNECT/blob/4.0.0/Product/Production/Common/CONNECTCoreLib/src/main/java/gov/hhs/fha/nhinc/callback/cxf/largefile/TimestampValidator.java And registering them in cxf: https://github.com/CONNECT-Solution/CONNECT/blob/CONNECT_integration/Product/Production/Gateway/DocumentSubmission_20/src/main/resources/docsubmission/_20/webservices.xml Hopefully, that will get you going. -- View this message in context: http://cxf.547215.n5.nabble.com/WSS4J-Timestamp-expiring-before-large-file-transfer-finishes-tp5717348p5723814.html Sent from the cxf-user mailing list archive at Nabble.com.
