Hi Dennis, all,
In my local trunk, I modified the RM-endpoints et al so that we have
one RMEndpoint per an application endpoint which handles all three
protocol variations. This RMEndpoint has the information about the
three protocol variations so that we can pass the protocol variation
instance t
Forgot the links:
http://svn.apache.org/viewvc?rev=1307112&view=rev
https://issues.apache.org/jira/browse/CXF-4215
Sergey
On 29/03/12 22:30, Sergey Beryozkin wrote:
Hi Oli,
I've moved the Claims annotations to the api module,
to the "org.apache.cxf.security.claims.authorization" package with
Hi Oli,
I've moved the Claims annotations to the api module,
to the "org.apache.cxf.security.claims.authorization" package with the
idea that the "org.apache.cxf.security.claims" package will hold in time
few common Claim data classes.
I reckon it should be enough for you to start experiment
Hi Dan
On 29/03/12 22:06, Daniel Kulp wrote:
OK. I'll drop the minimal bundle but keep the jaxrs. That works for me.
:-)
Thanks, I'll also play with the minimal osgi demo in the next few days
and see how it works without the jaxrs bundle.
Cheers, Sergey
Dan
On Wednesday, March 28, 201
OK. I'll drop the minimal bundle but keep the jaxrs. That works for me.
:-)
Dan
On Wednesday, March 28, 2012 04:39:30 PM Sergey Beryozkin wrote:
> Hi Dan
>
> On 28/03/12 16:16, Daniel Kulp wrote:
> > Quick question:
> > Are the jaxrs and minimal bundles still needed for 2.6.0? With the
Sure. We should likely move it from the sandbox into /cxf/fediz/trunk or
similar as well.
Dan
On Thursday, March 29, 2012 11:18:21 AM Oliver Wulff wrote:
> Hi all
>
> I've initially committed the fediz component to sandbox some months back:
> http://svn.apache.org/viewvc/cxf/sandbox/fediz/
On Thursday, March 29, 2012 02:36:55 PM Seumas Soltysik wrote:
> It would appear at this point that each async invocation involves a
> listener thread, waiting for a response from the server. Is there a way to
> configure the number of listener threads used by a particular client so
> that 100 asyn
It would appear at this point that each async invocation involves a
listener thread, waiting for a response from the server. Is there a way to
configure the number of listener threads used by a particular client so
that 100 async invocations do not result in 100 listener threads?
I was doing some
Hi Oli
thanks for initiating this thread
On 29/03/12 07:06, Oliver Wulff wrote:
Hi all
I'd like to start working on the RBAC (see mail "Role based access control with SAML
in CXF") and the Claims support for JAX-WS. Sergey has already implemented that for
JAX-RS.
I'd propose to move these c
Hi all
I've initially committed the fediz component to sandbox some months back:
http://svn.apache.org/viewvc/cxf/sandbox/fediz/
I'd like to come up with a roadmap for the fediz security component as proposed
by Colm in the following mail thread:
http://mail-archives.apache.org/mod_mbox/cxf-use
Hi Dan, Hi Guillaume,
Any update on this issue? We've run into the same issue ...
Best regards,
Andi
--
View this message in context:
http://cxf.547215.n5.nabble.com/Param-Headers-with-mustUnderstand-true-tp5512612p5603351.html
Sent from the cxf-dev mailing list archive at Nabble.com.
+1.
Colm.
On Thu, Mar 29, 2012 at 7:06 AM, Oliver Wulff wrote:
> Hi all
>
> I'd like to start working on the RBAC (see mail "Role based access control
> with SAML in CXF") and the Claims support for JAX-WS. Sergey has already
> implemented that for JAX-RS.
>
> I'd propose to move these classes
12 matches
Mail list logo
