Re: [OT] How to update the existing jar with Maven and then depend on it

2016-04-18 20:53 GMT+04:00 Sergey Beryozkin : > > Now, as far as my own practical requirement is concerned, this model needs > to be JPA persisted with OpenJPA. So I've spent a lot of time by > experimenting with the load time weaving with Spring ORM, which does not > seem

RE: WS-RM : Server sending LastMessage for SourceSequence termination back to itself.

My next question would be : Does the ws-rm persistence layer fully support request/response sequence persistence or only oneway sequence persistence ? From: Graeme Hill [graeme.h...@empired.com] Sent: 19 April 2016 10:08 To: users@cxf.apache.org Subject:

RE: WS-RM : Server sending LastMessage for SourceSequence termination back to itself.

On further investigation the issue has been narrowed down to the use of the persistence store via org/apache/cxf/ws/rm/persistence/jdbc/RMTxStore.java. If we remove the from the server blueprint the problem we were having no longer occurs i.e. lastMessage for the server held source sequence is

Web Service with WS-SecurityPolicy (sign body + timestamp)

Hi, I'm looking within the CXF Code project about an example where the TimeStamp and Body of the SOAP request is signed according to a Web Security Policy Here is the request equivalent populated with WSS4J without a policy defined within the WSDL file

[OT] How to update the existing jar with Maven and then depend on it

Hi I thought I'd ask at the users list first, sorry for the noise. I have the following task: make sure that a CXF OAuth2 model (cxf-rt-rs-security-oauth2 module) can be persisted with JPA. Right now the tests are running and use Hibernate, but also can be switched to use OpenJPA. The

RE: WS-RM : Server sending LastMessage for SourceSequence termination back to itself.

Thanks Aki. The major differences between the demos and our actual use: 1) We are using a WS-RM persistence store ported from org/apache/cxf/ws/rm/persistence/jdbc/RMTxStore.java 2) All of our incoming requests/responses use WS-Security headers We suspect the issue possibly lies within there

Re: WS-RM : Server sending LastMessage for SourceSequence termination back to itself.

Hi Graeme, You can apply the same modification (http://pastebin.com/BwTGt9qC) that I applied to cxf-2.7.x's ws_rm sample to cxf-2.7.0's ws_rm sample to trigger the server termination to see if there is a difference between the latest 2.7.x and 2.7.0. If none, something else is causing the strange