Mailing-List: contact cxf-issues-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cxf-dev@incubator.apache.org
Message-ID: <31679669.1180531936571.JavaMail.jira@brutus>
Date: Wed, 30 May 2007 06:32:16 -0700 (PDT)
From: "Andrea Smyth (JIRA)" <jira@apache.org>
To: cxf-issues@incubator.apache.org
Subject: [jira] Resolved: (CXF-139) Port Celtix RM Persistence Handler to
 CXF
In-Reply-To: <2434333.1159786219575.JavaMail.root@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Andrea Smyth resolved CXF-139.
------------------------------

    Resolution: Fixed

> Port Celtix RM Persistence Handler to CXF
> -----------------------------------------
>
>                 Key: CXF-139
>                 URL: https://issues.apache.org/jira/browse/CXF-139
>             Project: CXF
>          Issue Type: Sub-task
>          Components: WS-* Components
>    Affects Versions: 2.0-M1
>            Reporter: Andrea Smyth
>            Assignee: Andrea Smyth
>             Fix For: 2.0
>
>
> Implement as SOAP interceptor. Possibly requires a new phase as this handler should be last in the chain - may be add it dynamically? Actually, only one of the three interceptors may need to be added -  this can then take care of adding the others (provided they have not been added yet). Makes configuration easier.
> There is a risk associated with this task as the persistance handler logic entailed some form of unmarshaling/remarshaling - need to check ow this works out in the CXF architecture.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.