Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Message-ID: <31916071.1170256027292.JavaMail.jira@brutus>
Date: Wed, 31 Jan 2007 07:07:07 -0800 (PST)
From: "Davanum Srinivas (JIRA)" <jira@apache.org>
To: axis-dev@ws.apache.org
Subject: [jira] Updated: (AXIS2-1069) Message Driven Bean as JMS listener
In-Reply-To: <4057254.1156450557170.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Davanum Srinivas updated AXIS2-1069:
------------------------------------

    Assignee: Sanka Samaranayake

> Message Driven Bean as JMS listener
> -----------------------------------
>
>                 Key: AXIS2-1069
>                 URL: https://issues.apache.org/jira/browse/AXIS2-1069
>             Project: Axis 2.0 (Axis2)
>          Issue Type: New Feature
>          Components: transports
>            Reporter: Ali Sadik Kumlali
>         Assigned To: Sanka Samaranayake
>         Attachments: AxisMdb.java
>
>
> I've been walking around mdb implementation for Axis2 for a while. And at last, I've successfully served my services through it. But there are many concerns that need to be taken into account when it comes to J2EE environment.
> My purpose for creating this issue is sharing my mdb code and starting a discussion around:
> - Application server agnostic packaging and deployment model
> - Necessity of listener manager integration
> - Supporting JMS 1.0.2b as well
> - TODO comments I've put into the mdb file
> Let me list my way I've come through:
> - Chose "njms" as base implementation.
> - Used geronimo-spec-ejb-2.1-rc4.jar to be able to compile MDB code
> - Mixed some code from AxisServlet, JMSListener, JMSMessageReceiver, JMSConnectionFactory and put them into AxisMdb.
> - Used WL8.1 which support JMS 1.0.2b API. But "njms" requires JMS 1.1.
> - Used Sonic 7.0's client jars as JMS API 1.1 implementation and overrided WL's client by putting them in system classpath
> - Put all the jars come with Axis2 under APP-INF/lib folder found in ear file. Please note that *this is WL specific* solution. Otherwise, I needed to add all the jars into system classpath. But, in that case, I got operating system error that complained about size of the CLASSPATH variable.
> - Created an ear as following structure:
>   - APP-INF
>     - lib
>   - META-INF
>   - ejb-module.jar
>     - org/apache/axis2/transport/njms/AxisMdb.class
> - Instead of giving absolute path for repository in the code, I only used directory name (server_repo) and created the directory under "C:\bea\user_projects\domains\testserver\ ". This is the folder WL's starting and stopping scripts reside. When Axis2 is initializing, this folder found successfully.
> Since I don't know all the details of Axis2, need to be directed towards a better code. I hope someone will look into the file I'll attach and give feedback.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org