Hi Colm,
I tried using CXF 2.5.3-SNAPSHOT for the latest changes, including the
WSS4J 1.6.5 nightly build. This looks much better, getting as far as
verifying the UsernameToken on the server before dying with a data
reference error:
Caused by: org.apache.ws.security.WSSecurityException: An error
Wow, thanks Colm :-) The black magic security stuff in action :-)
Cheers, Sergey
On 24/02/12 12:17, cohei...@apache.org wrote:
Author: coheigea
Date: Fri Feb 24 12:17:22 2012
New Revision: 1293213
URL: http://svn.apache.org/viewvc?rev=1293213view=rev
Log:
Fixed failing RS-Security tests with
Hi all
I've got an issue with a mustUnderstand SOAP Header that is used as service
parameter (it's a method parameter of the implementor).
As the MustUnderstandInterceptor is placed in the PRE_PROTOCOL phase, the
binding operation is not known at this time (except if there is a
SOAPAction header
Hi,
I am running into an issue with trying to add WS security to my CXF client.
Any help is appreciated.
Problem: I have a CXF client prototype that sends a request using MTOM. It
runs inside a WAS (Websphere application server) server. Right now, I am
prototyping this locally on a local WAS
Hi,
As you know CXF 2.5.3-SNAPSHOT is moving to use WSS4j 1.6.5-SNAPSHOT
I'm trying to install the WSS4J feature of CXF-2.5.3-SNAPSHOT, and I get
the complain about packages of xmlsec cannot be resolved.
I compared the META-INF of the WSS4J 1.6.5-SNAPSHOT and WSS4j 1.6.4 and
found the
On Friday, February 24, 2012 11:43:30 PM Willem Jiang wrote:
Hi,
As you know CXF 2.5.3-SNAPSHOT is moving to use WSS4j 1.6.5-SNAPSHOT
I'm trying to install the WSS4J feature of CXF-2.5.3-SNAPSHOT, and I get
the complain about packages of xmlsec cannot be resolved.
I compared the META-INF
Just a quick follow up...
I chatted with Guillaume a bit on IRC this morning about this. I don't see a
major issue with moving it. The only potential problem I see is that this
moves the interceptor to running after the JAX-WS SOAPHandlers which could
potentially cause TCK issues with
Hi Sergey,
I was having a problem in building 2.5.x and trunk in a restricted
fresh environment, then I noticed that systests/rs-security was still
referring to cxf-rt-rs-security-oauth-test which no longer existed in
2.5.x and trunk. I saw the corresponding classes now exist in
You may also have better luck if you replace the saaj-impl and jaxp-ri jars
with just the servicemix bundle jar from:
http://repo1.maven.org/maven2/org/apache/servicemix/bundles/org.apache.servicemix.bundles.saaj-
impl/1.3.18_1/
It includes the parts of jaxp-ri that are required by saaj, but
Hi Aki
On 24/02/12 21:14, Aki Yoshida wrote:
Hi Sergey,
I was having a problem in building 2.5.x and trunk in a restricted
fresh environment, then I noticed that systests/rs-security was still
referring to cxf-rt-rs-security-oauth-test which no longer existed in
2.5.x and trunk. I saw the
Dan,
just to confirm, the only way to make application jars to be loaded ahead of
IBM jars is changing in server console classes loaded with Application
class loader first ? or is there any other way?
Thanks
Kumar
--
View this message in context:
Hi Tom,
Could you please explain how you made jars to be loaded ahead of IBM jars?
Thanks
Kumar
--
View this message in context:
http://cxf.547215.n5.nabble.com/Question-about-enabling-WS-Security-in-CXF-Webshpere-tp5513025p5514139.html
Sent from the cxf-dev mailing list archive at
12 matches
Mail list logo