Hello,John Li said
John Li wrote
I have been working with the WSRM implementation of Apache CXF and now
I'mcombining it with WS-Security. After a struggle the createSequence call
issuccessfully finished with WS-Security added [...]
I am fighting with the same problem. When working with WS-RM
Hi Carlos,
I'm working on fixing these issues now, specifically on the combination
of WS-RM with WS-SecureConversation. This is the configuration specified
by the WS-I Reliable Secure Profile
(http://www.ws-i.org/Profiles/ReliableSecureProfile-1.0-2010-11-09.html).
But you left out the
Hello Dennis,
The error was missed in the conversion from Nabble to mail. This is what
appears when WS-RM interceptor tries to send the createSequence message:
10:18:48.328 [main] ERROR org.apache.cxf.ws.rm.Proxy - Failed to send RM
protocol message
Hi,
I got the same issue as described in this mail. And svc.addPort code seems
to be only needed for MTOM service. The non-MTOM service is working without
this code.
Can anyone confirm that is should be fixed? Seems needs to run the TCK with
this change.
--
View this message in context:
Although there are problems in using WS-RM and WS-Security together with
the existing code I don't think this is one of them. If you look back to
John's original post, his issue was that the timestamp was not being
updated on retransmissions. This looks like more of a configuration issue.
I'm
Hi Jason,
I suppose you haven't had time for this.
Since I see Dan preparing for the 2.7.x release today, I would like to
include this ehcache fix in the release if we still got time so that
we can use cxf 2.7.6 with a newer ehcache. I made a local change for
trunk (not updating the ehcache
Hello,
Thank you for your response.
John said in his very first comment After a struggle the createSequence
call is
successfully finished with WS-Security added. I think his original problems
where the same as I am having right now. Maybe I should open a new thread to
treat the problems of
Hi,
No sorry have not had a chance to look at this at all. My day job is
keeping me really busy, now on java 7 upgrade and all the fun that comes
with it.
I had a look at the patch. It's unfortunate that we have to use
reflection, but I was pleased to see this all in the EHCacheUtils class, so
I've been searching for ways to remove the WSA Addressing Property ReplyTo
from the Client Outbound as the WebService does not require ReplyTo for
synchronous messages.
I've created outbound interceptors (from simple to saaj) and tried many
Phases but to no avail. Any help will be very much
Perhaps John can tell you what he did to get it working. I'll check into
that myself next week.
Thanks,
- Dennis
On 07/16/2013 11:54 PM, Carlos Aza wrote:
Hello,
Thank you for your response.
John said in his very first comment After a struggle the createSequence
call is
successfully
10 matches
Mail list logo
