cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aki Yoshida (Resolved) (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CXF-4218) Change RMEndpoint and RMStore so that the sequences are recovered with the correct protocol versions and monitored under their endpoint
Date Mon, 02 Apr 2012 11:29:22 GMT

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

Aki Yoshida resolved CXF-4218.
------------------------------

    Resolution: Fixed

This change required a DB schema change. Therefore, the change was made only in 2.6.0. For
2.5.x, a minor change was made to only avoid the jmx registration error by registering the
endpoints with the default protocol variation only.


                
> Change RMEndpoint and RMStore so that the sequences are recovered with the correct protocol
versions and monitored under their endpoint
> ---------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CXF-4218
>                 URL: https://issues.apache.org/jira/browse/CXF-4218
>             Project: CXF
>          Issue Type: Improvement
>          Components: WS-* Components
>    Affects Versions: 2.5.2
>            Reporter: Aki Yoshida
>            Assignee: Aki Yoshida
>             Fix For: 2.6
>
>
> Currently, the WS-RM protocol variation information (or more precisely, the used WS-RM
and WS-A version information) is not persisted. 
> We need to persist the WS-RM protocol variation information in RMStore so that we can
recover the sequences with their original protocol versions after system recovery. 
> In addition, we should assign a single RMEndpoint to an application endpoint to handle
all protocol variations so that we can manage the recovery and JMX management of those sequences
belonging to this endpoint over this single RMEndpoint. 

--
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

        

Mime
View raw message