[
https://issues.apache.org/jira/browse/CXF-1147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jeff Yu updated CXF-1147:
-------------------------
Fix Version/s: (was: 2.1)
2.0.3
> Refactoring the jca handler chain building.
> -------------------------------------------
>
> Key: CXF-1147
> URL: https://issues.apache.org/jira/browse/CXF-1147
> Project: CXF
> Issue Type: Sub-task
> Components: Integration
> Affects Versions: 2.0.2
> Environment: windows
> Reporter: Jeff Yu
> Assignee: willem Jiang
> Fix For: 2.0.3
>
> Attachments: cxf-1147.patch
>
>
> Now, the cxf uses hard-coded configuration in InvocationHandlerFactory class
> to build the jca handler chain as follow:
> String[] classNames =
> {"org.apache.cxf.jca.cxf.handlers.ProxyInvocationHandler",
>
> "org.apache.cxf.jca.cxf.handlers.ObjectMethodInvocationHandler",
>
> "org.apache.cxf.jca.cxf.handlers.InvokingInvocationHandler"};
> It would be better for us to build the handler chain from configuration file,
> such as META-INF/org.apache.cxf.jca.handlers in classpath.
> so if we add another jca module jar, say jca-security, we don't need to
> override the InvocationHandlerFactory to add the jca-security Hanlder,
> we just need to add the org.apache.cxf.jca.handlers in jca-security jar, so
> it can be integrated seamless.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
