On Oct 8, 2008, at 5:16 PM, Sergey Beryozkin wrote:
Hi
I agree with what Dan suggested - logging a message in a
PolicyVerificationOutInterceptor should suffice in most cases. Few
more
comments.
I think that asserting a policy on the outbound path makes sense
only if
a specification for
Doh! That was supposed to be [{foo:Bar}, {bling}Blang]
On Oct 9, 2008, at 9:44 AM, Fred Dushin wrote:
And on the outbound side you'd get [{foo:Bar}, {gnu}Gnat]
Hi Fred
I strat thinking this message gets a bit off-track :-) Few more comments.
That's fine, in that the AssertionBuilder can render a decision about what interceptors to add to the chain. But that won't
solve the bug I've identified.
As we've said many times what will solve this
Hi,
I'd like to try to summarize what we've talked at this thread. Fred - please
feel free to challenge what I'm about to say :-)
Original problem : server-side outbound Policy interceptor assumes that no
policy alternative has been asserted on the outbound path and reports a
failure by
This is a continuation of the discussion at
http://mail-archives.apache.org/mod_mbox/cxf-dev/200808.mbox/[EMAIL PROTECTED]
I've confirmed that this is still an issue in 2.2-SNAPSHOT, and I'd
like to start a discussion of solutions. I'll start by describing the
policy framework
:02
To: [EMAIL PROTECTED]
Subject: More on server response policies
This is a continuation of the discussion at
http://mail-archives.apache.org/mod_mbox/cxf-dev/200808.mbox/%3c3AAFD5B7-693
[EMAIL PROTECTED]
I've confirmed that this is still an issue in 2.2-SNAPSHOT, and I'd
like to start
