Hi Dennis, While ago, I mentioned the problem that I was having with the protocol variations in WS-RM.
http://cxf.547215.n5.nabble.com/a-quesiton-on-CXF-2-5-WS-RM-s-protocol-variation-handling-td4710027.html I would like to come back to this problem, as I am having a few problems with server side sequence and message recoveries. To begin with, I assume we can assign a specific protocol variation to a particular sequence. In other words, we can assume each sequence has a fixed protocol version that was used to create that sequence. However, this assumption is broken at the RM endpoint recovery. For the client endpoints, the sequences are assigned to the configured static protocol variation. If you dynamically changed the protocol variation, your sequence would be reassigned to the wrong protocol variation. For the server endpoints, the sequences are replicated for each protocol variation and simply assigned to their original protocol variations. And this latter is causing an issue in several areas such as - the RM endpoint registration in JMX (because each endpoint gets registered for three variations) - each stored message gets recovered per each variation (this only happens at the server side because the server side code is explicitly starting each endpoint per protocol variant).. To solve these issues, I would like to have one RM endpoint that can support a different protocol variation per sequence. We must also store the protocol variation in the RMStore so that the sequence and message recoveries will find the correct protocol variations at restart. How do you think? Thanks. Regards, Aki
