What version of CXF and WSS4J are you using? This may actually be fixed in
CXF 2.4.1 as WSS4J calls back out to CXF to create the crypto if it's null.
If this is still occurring in 2.4.x, I'd love to see a testcase.
Dan
On Thursday, August 11, 2011 6:11:56 AM ovi wrote:
> When I have the po
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 wrote:
> to solve this problem I have
> 1. a client that reads the wsdl and policies and sends the message to the
> server. This is the normal way to work wi
to solve this problem I have
1. a client that reads the wsdl and policies and sends the message to the
server. This is the normal way to work with wsdls with policies.
2. for the server side because of the bug mentioned that no Signature is
created as an action, we use the programatic approach whe
+1
Freeman
On 2011-8-12, at 上午1:07, Daniel Kulp wrote:
We've resolved over 90 issues since 2.4.1 and thus is time for a
release and
over 40 issues ported back for 2.3.5.
This build fixes the issue found with JAX-RS services in Camel that
occurred
with Camel.
List of issues:
2.4.2:
h
Ran some tests in camel trunk with CXF 2.4.2 they are looking good :).
Here are my +1,
Willem
On 8/12/11 1:07 AM, Daniel Kulp wrote:
We've resolved over 90 issues since 2.4.1 and thus is time for a release and
over 40 issues ported back for 2.3.5.
This build fixes the issue found with JAX-
