Yes, I don't remember offhand how, have a look at the JAX-WS docs please, I think it can be injected through a field or through a
setter. Perhaps using a setter is better in cases like this, as you can then extract the common info from either JAX-WS
WebServiceContext or JAX-RS SecurityContext.
Perhaps, in the future, things like SecurityContext in both JAX-WS and JAX-RS can rely on some shared (CXF utility) code so that
they can be casted to a common class to be used by the application...
Cheers, Sergey
----- Original Message -----
From: "John-M Baker" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Monday, June 23, 2008 9:36 AM
Subject: Re: Roles and permissions
And how is that done? Via a set method of some kind?
John Baker
--
Web SSO
IT Infrastructure
Deutsche Bank London
URL: http://websso.cto.gt.intranet.db.com
Daniel Kulp <[EMAIL PROTECTED]>
20/06/2008 18:13
Please respond to
[email protected]
To
[email protected]
cc
Subject
Re: Roles and permissions
On Jun 20, 2008, at 11:23 AM, John-M Baker wrote:
Hi,
What was the solution to this problem? Only apply it to the REST
service?
Will a future release of CXF fix it for SOAP?
Well, JAX-WS has it's own security stuff. Thus, for jax-ws/soap,
you would need the WebServiceContext injected which has the principal/
role on it.
Dan
----------------------------
IONA Technologies PLC (registered in Ireland)
Registered Number: 171387
Registered Address: The IONA Building, Shelbourne Road, Dublin 4, Ireland
