Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Fri, 17 Jun 2011 13:45:47 +0000 (UTC)
From: "Aki Yoshida (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: 
 <1254929603.14986.1308318347486.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <381580950.11277.1308238787340.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (CXF-3597) WS-RM client keeps using an expired
 source sequence
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Aki Yoshida resolved CXF-3597.
------------------------------

    Resolution: Fixed

> WS-RM client keeps using an expired source sequence
> ---------------------------------------------------
>
>                 Key: CXF-3597
>                 URL: https://issues.apache.org/jira/browse/CXF-3597
>             Project: CXF
>          Issue Type: Bug
>          Components: WS-* Components
>    Affects Versions: 2.4, 2.3.4
>            Reporter: Aki Yoshida
>            Assignee: Aki Yoshida
>             Fix For: 2.4.2, 2.5
>
>
> The WS-RM client does not check if the current source sequence has expired or not. Consequently, the client keeps using the expired source sequence to transmit the messages.
> When the current sequence has been expired, a new sequence should be created as in the handling of the very first message.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira