Hi Colm- I've been thinking about this a bit, and I'm leery of the interop implications of this change. The fact that the cxf-sts does not realize this interpretation of the specification makes me nervous. Compliance with WS-Trust, a spec whose schema definitions specify unbounded collections of xs:any types for requests and responses seems to be driven largely by convention. Nor does the validate binding in WS-Trust mention much about what I've outlined above. I don't doubt that this could be added to the cxf-sts code-base, and that it might provide value to some customers, but the more value it provided, the more likely that it would be consumed from a heterogeneous (e.g. .NET) context, with remote prospects of either semantic congruence, or the ability of effecting said congruence by diving into the WCF (or whatever) code base and making the necessary changes.
Thanks for the discussion. Dirk -- View this message in context: http://cxf.547215.n5.nabble.com/STS-Validate-Operation-and-token-transformation-tp5753327p5753940.html Sent from the cxf-user mailing list archive at Nabble.com.
