Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Message-ID: <1672389001.1221505904311.JavaMail.jira@brutus>
Date: Mon, 15 Sep 2008 12:11:44 -0700 (PDT)
From: "William Tam (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Subject: [jira] Updated: (CXF-1801) JCA inbound connector does not support
 WebSphere 6.1
In-Reply-To: <2085754580.1221505307857.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

William Tam updated CXF-1801:
-----------------------------

    Attachment: CXF-1801.patch

I created a patch with 3 samples.  I stuck the geronimo-ejb api jar that is needed by the samples in  distribution\src\main\release\samples\integration\jca\common\lib\geronimo-ejb_3.0_spec-1.0.1.jar.  I can't think of better way to include but it's got to be a better way.

> JCA inbound connector does not support WebSphere 6.1
> ----------------------------------------------------
>
>                 Key: CXF-1801
>                 URL: https://issues.apache.org/jira/browse/CXF-1801
>             Project: CXF
>          Issue Type: New Feature
>          Components: Integration
>         Environment: IBM WebSphere 6.1
>            Reporter: William Tam
>             Fix For: 2.2
>
>         Attachments: CXF-1801.patch
>
>
> The current JCA inbound connector relies on service endpoint interface classes being available to its context classloader which is not necessary that case.  CXF should consider moving away from the proprietary activation method with ejb_servant.properties to a method that leverages the JCA 1.5 spec using with Message Driven Bean.

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