Hi Freeman,
I'm -1 to the way you are configuring this patch. WSS10 and WSS11 are
standard policies defined in the WS-SP 1.3 spec, and so it's not a
good idea to add a custom policy for these.
The best way to configure it is to define a (boolean) tag in
SecurityConstants so that it can be set as
Hi Colm,
Thanks for the input, will revise it accordingly.
Freeman
On 2012-2-20, at 下午6:06, Colm O hEigeartaigh wrote:
Hi Freeman,
I'm -1 to the way you are configuring this patch. WSS10 and WSS11 are
standard policies defined in the WS-SP 1.3 spec, and so it's not a
good idea to add a
Hi,
Just collected experience regarding WS-policy in CXF in following article:
https://cwiki.apache.org/confluence/display/CXF/Using+WS-Policy+in+CXF+projects
Notes, remarks, corrections are welcome.
Regards,
Andrei.
Hi
I've started working on the initial OAuth 2.0 support to be available in
CXF 2.6.0 [1].
We already provide OAuth 1.0 support starting from CXF 2.5.0 [2] - this
has been continuously enhanced during the last few months and I think it
is capable enough for users seeking to write OAuth 1.0
Hi David
On 19/02/12 00:42, David Bosschaert wrote:
Hi all,
I was recently running the CXF-DOSGi 1.3 release through the OSGi TCK
to make sure it's still compliant with the spec.
It turned out that the changes made between 1.2 and 1.3 cause a number
of TCK failures, so I've been looking at
