Re: a quesiton on CXF 2.5 WS-RM's protocol variation handling

Hi Aki, On 08/18/2011 09:25 AM, Aki Yoshida wrote: > ... > > RMManager now manages endpoints under each supported protocol > variation using Map>. > Does this mean that an Endpoint can be used in several protocol variations? Yes. I decided to take this approach because I wanted the WS-RM serversi

a quesiton on CXF 2.5 WS-RM's protocol variation handling

Hi Dennis, I am trying to adjust my JMX code for the CXF 2.5 WS-RM and I have a question. RMManager now manages endpoints under each supported protocol variation using Map>. Does this mean that an Endpoint can be used in several protocol variations? The background to my question is that I want to

Re: EndorsingSupportingTokens and SignedSupportingTokens throing a Nullpointer exception

On Fri, Aug 12, 2011 at 12:56 PM, Colm O hEigeartaigh-2 [via CXF] < ml-node+4692834-2005679887-238...@n5.nabble.com> wrote: > Hi, > > Could you create a JIRA for this attaching the WSDL and I'll take a > look at it next week. > > Colm. > > On Fri, Aug 12, 2011 at 10:51 AM, ovi <[hidden > email]

Re: EndorsingSupportingTokens and SignedSupportingTokens throing a Nullpointer exception

thanks for the reply. I will take a look. By the way here we are bound to use cxf 2.3.1 because cxf 2.4.x is not in jboss 6.0.0.Final (the one we sue) and only in jboss 7.0.x but this one is not ee compliant yet. So we have the hibrid solution that I proposed and that works for now. When we migrat

Re: best practice for setting order constraints among interceptors

Hi Dan, thanks for the very good explanation about its history and its evolution theory. regards, aki 2011/8/16 Daniel Kulp : > > For the most part, I don't think it really matters.  There used to be some > performance issues adding interceptors that had a bunch of befores and afters, > but those