You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Jervis Liu (JIRA)" <ji...@apache.org> on 2006/09/12 10:13:24 UTC

[jira] Created: (CXF-73) a configuration to configure interceptor chain

a configuration to configure interceptor chain
----------------------------------------------

                 Key: CXF-73
                 URL: http://issues.apache.org/jira/browse/CXF-73
             Project: CeltiXfire
          Issue Type: Sub-task
          Components: Configuration
    Affects Versions: 2.0-M1
            Reporter: Jervis Liu


all the interceptor chain participation is currently API-driven - i.e. inpterceptors are added to the relevant chains programmatically via InterceptorProvider.get{In|Out|Fault}Interceptors().add() as opposed to a configuration-driven mechanism. The latter will be increasingly called
for in order to engage the RM interceptors, as one of the goals of Celtix RM support was to allow reliability to be introduced without any changes to application code

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Closed: (CXF-73) a configuration to configure interceptor chain

Posted by "Andrea Smyth (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/CXF-73?page=all ]

Andrea Smyth closed CXF-73.
---------------------------

    Resolution: Fixed

CXF-73 is one aspect of CXF-100.

> a configuration to configure interceptor chain
> ----------------------------------------------
>
>                 Key: CXF-73
>                 URL: http://issues.apache.org/jira/browse/CXF-73
>             Project: CeltiXfire
>          Issue Type: Sub-task
>          Components: Configuration
>    Affects Versions: 2.0-M1
>            Reporter: Jervis Liu
>
> all the interceptor chain participation is currently API-driven - i.e. inpterceptors are added to the relevant chains programmatically via InterceptorProvider.get{In|Out|Fault}Interceptors().add() as opposed to a configuration-driven mechanism. The latter will be increasingly called
> for in order to engage the RM interceptors, as one of the goals of Celtix RM support was to allow reliability to be introduced without any changes to application code

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira