This option should fix the ordering issue at least because at the moment CXF gets the union of all the assertions included in multiple alternatives.
Not sure about the dynamic selection at the runtime though.... cheers, Sergey On Fri, Feb 25, 2011 at 11:15 AM, Sergey Beryozkin <[email protected]> wrote: > Hi > > On Fri, Feb 25, 2011 at 11:04 AM, Rhenius, Karl Stefan <[email protected]> wrote: >> >>> > I'm going to make a testcase for jira. >>> >>> Yea. Please do. This definitely sounds like a bug, but a >>> complicated enough >>> one that a good test case is probably required. >> >> Hi Dan, >> >> the jira issue is here: https://issues.apache.org/jira/browse/CXF-3365 >> >> I noticed, that the ordering of policies affects the response too. >> Defining SecureConversation as 2nd policy causes a bug during the >> RST/SCT message. >> > Dynamically choosing the right alternative is tricky/complex. > > In fact, I'm wondering, if your policy is totally correct. > Given that you expect the secure conversation flow all the time, > should it look like this instead: > > <Policy> > <ExactlyOnce> > <SecureConverstaion/> > </ExactlyOnce> > <ExactlyOnce> > <SecureConverstaion/> > <UT/> > </ExactlyOnce> > </Policy> > > What do you think ? Wondering if it will work... > > cheers. Sergey > >> cheers >> Karl >> >
