Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Mon, 5 Mar 2012 23:53:57 +0000 (UTC)
From: "Aki Yoshida (Updated) (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: 
 <421785919.24881.1330991637397.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1739704919.24831.1330991157217.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (CXF-4164) Robust-InOnly processing with WS-RM
 must must delay updating the sequence until message delivery
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/CXF-4164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Aki Yoshida updated CXF-4164:
-----------------------------

    Summary: Robust-InOnly processing with WS-RM must must delay updating the sequence until message delivery  (was: Robust-InOnly processing with WS-RM must must wait for updating the sequence until message delivery)
    
> Robust-InOnly processing with WS-RM must must delay updating the sequence until message delivery
> ------------------------------------------------------------------------------------------------
>
>                 Key: CXF-4164
>                 URL: https://issues.apache.org/jira/browse/CXF-4164
>             Project: CXF
>          Issue Type: Bug
>          Components: WS-* Components
>    Affects Versions: 2.4.7, 2.5.3
>            Reporter: Aki Yoshida
>            Assignee: Aki Yoshida
>             Fix For: 2.4.7, 2.5.3, 2.6
>
>
> A recently added robust-inonly mode (CXF-4096) can be used to invoke services synchronously so that the caller can distinguish a successful invocation from an unsuccessful one. 
> Although this feature is implemented independently of WS-RM, it can be used with WS-RM to force the acknowledgement message to be returned only after the service invocation successfully completes. 
> Unfortunately, there is a minor change required in WS-RM so that this feature will work for this use case. Namely, it must be made aware of this robust setting so that it can postpone updating the sequence until the message is delivered.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira