cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CXF-2367) Clean up JCA connector impls
Date Fri, 09 Sep 2011 18:49:08 GMT

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

Daniel Kulp resolved CXF-2367.
------------------------------

       Resolution: Won't Fix
    Fix Version/s: Invalid


This improvement request has been open for years and no-one has stepped up to implement it.
As such, it does not seems to be a priority for the existing CXF community. If, in the future,
someone would like to tackle this, feel free to open is and attach a patch.

> Clean up JCA connector impls
> ----------------------------
>
>                 Key: CXF-2367
>                 URL: https://issues.apache.org/jira/browse/CXF-2367
>             Project: CXF
>          Issue Type: Task
>          Components: Integration
>         Environment: JBoss and WebSphere
>            Reporter: William Tam
>            Priority: Minor
>             Fix For: Invalid
>
>
> Currently, there are two implementations of JCA connector.  The new one was added to
address issues when deploying in WebSphere without destabilizing the support for JBoss.  The
new impl takes advantage of JCA 1.5 spec such as MDB message inflow and endpoint de/activation.
 It removes the proprietary ejb_servants.properties for activation.  We should test the new
impl with JBoss and update samples/wiki.  Once that is done, we should end-of-life the old
impl.  They do share a common code.  The new impl just added two packages org.apache.cxf.jca.inbound
and outbound.

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

        

Mime
View raw message