[
https://issues.apache.org/jira/browse/AXIS2-3662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12585893#action_12585893
]
Asankha C. Perera commented on AXIS2-3662:
------------------------------------------
Hi George
Actually I looked into two other implementations and it seems they both use the
'polling' approach. I do not think the MDB approach can work at all - for
Apache Synapse, which uses the JMS transport a lot, thus to keep the core code
executable within and outside of a JEE app server, I thought of using polling
within and async outside and to decide on this at runtime. I also need to keep
backward compatibility with JMS 1.0.x and also add support for transactional
JMS. So I will be doing some enhancements pretty soon - initially into the
version within Synapse, and then contribute this to Axis2 as well
asankha
> Can't use JMS transport from axis2.war on WebSphere Application Server 6.1
> --------------------------------------------------------------------------
>
> Key: AXIS2-3662
> URL: https://issues.apache.org/jira/browse/AXIS2-3662
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Affects Versions: 1.3
> Environment: WebSphere Application Server 6.1, Axis2 war deployment
> Reporter: George Marrows
>
> From
> http://www.nabble.com/setMessageListener-not-permitted-in-Websphere-td15306747.html:
>
> > We are currently deploying axis2 in Websphere 6.1. We wish to
> > use the jms transport. However axis2 fails to start because
> > it uses forbidden api's.
> >
> > On startup axis2's JMSConnectionFactory class calls the
> > listenOnDestination(String destinationJndi) method. Here it
> > creates a MessageConsumer and calls the
> > MessageConsumer.setMessageListener(MessageListener listener)
> > method. This causes failure and the exception thrown is as follows:
> > javax.jms.IllegalStateException: Method setMessageListener
> > not permitted
> >
> > On looking through docs online it is clear that IBM have
> > stuck to the J2EE
> > 1.4 specification. This states that the
> > MessageConsumer.setMessageListener(MessageListener listener)
> > method can not be called in a Web or EJB container. See
> > http://www.ibm.com/developerworks/library/j-getmess/ for details.
> [See http://java.sun.com/j2ee/j2ee-1_4-fr-spec.pdf, section 6.6 for the
> actual spec reference.]
> This means that the only way of deploying Axis2 with JMS transport on WAS is
> to use the standalone axis server. This works, but a deployment within the
> application server would be greatly preferable.
--
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
