I would look for:
a)CL cant find the class
b)CL cant instantiate the object with supplied configuration
the stock axis2.xml configuration implements JMSListener with a default
parameter name e.g.
<transportReceiver name="jms"
class="org.apache.axis2.transport.jms.JMSListener">
<parameter name="default">
<parameter
name="java.naming.factory.initial">org.apache.activemq.jndi.ActiveMQInitialContextFactory</parameter>
<parameter
name="java.naming.provider.url">tcp://localhost:61616</parameter>
<parameter
name="transport.jms.ConnectionFactoryJNDIName">QueueConnectionFactory</parameter>
</parameter>
</transportReceiver>
and the specific services.xml configuration would look something like
<service name="echo">
<transports>
<transport>jms</transport>
</transports>
<parameter name="transport.jms.ConnectionFactory"
locked="true">default</parameter>
<parameter name="transport.jms.Destination"
locked="true">dynamicTopics/something.TestTopic</parameter>
</service>
where if a transport.jms.destination is not specified, the
implementation would create a JMS Queue with the service name. e.g. echo
does this help?
Martin
______________________________________________
Disclaimer and confidentiality note
Everything in this e-mail and any attachments relates to the official business
of Sender. This transmission is of a confidential nature and Sender does not
endorse distribution to any party other than intended recipient. Sender does
not necessarily endorse content contained within this transmission.
To: [email protected]
Subject: RE: MDB and Axis2
From: [EMAIL PROTECTED]
Date: Wed, 6 Aug 2008 19:53:27 +0530
Now here is the case - I uncommented that
part also in the axis2.xml present in the jar files. That gave me the issue
I mentioned earlier. Now I created a conf directory and placed the modified
axis2.xml there (guess thats the better way of doing things). This time
I got an error that says
javax.jms.ConnectionFactory.createConnection()Ljavax/jms/Connection.
So I got the jms-1.1.jar from the Spring 2.5.4 distribution and replaced
the existing jms.jar under WEB-INF\lib. But the
javax.jms.ConnectionFactory.createConnection
issue persists. Any idea?
Regards,
Saurav Chatterjee
US IT DS Service Oriented Architecture (SOA)
Development Team | Saurav
Chatterjee | PriceWaterhouseCoopers
LLP | Office: +91-033-2341-3140
| Cell: +91-9830868384 | | SOA Support: 813-348-7600 |
Martin Gainty <[EMAIL PROTECTED]>
08/06/2008 07:16 PM
Please respond to
[email protected]
To
<[email protected]>
cc
Subject
RE: MDB and Axis2
Hello
what happens when you implement listener in axis2.xml with
<transportReceiver name="jms"
class="org.apache.axis2.transport.jms.JMSListener">
?
Martin
______________________________________________
Disclaimer and confidentiality note
Everything in this e-mail and any attachments relates to the official business
of Sender. This transmission is of a confidential nature and Sender does
not endorse distribution to any party other than intended recipient. Sender
does not necessarily endorse content contained within this transmission.
To: [email protected]
Subject: Fw: MDB and Axis2
From: [EMAIL PROTECTED]
Date: Wed, 6 Aug 2008 17:12:08 +0530
Also, I am getting this exception at the console although I have uncommented
the jms transport in both axis2-1.4.jar and axis2-kernel-1.4.jar. Note
that AsynchronousResponseGenerator is the class name I am using as the
listener.
org.apache.axis2.deployment.DeploymentException: Service [
AsynchronousResponseGenerator]
is trying to expose in a transport : <transports>
<transport>jms</transport>
</transports> and which
is not available in Axis2
at
org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:151)
at
org.apache.axis2.deployment.ServiceDeployer.deploy(ServiceDeployer.java:81)
at
org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
at
org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:597)
at
org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
at
org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:330)
at
org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:227)
at
org.apache.axis2.deployment.DeploymentEngine.loadServices(DeploymentEngine.java:131)
at
org.apache.axis2.deployment.WarBasedAxisConfigurator.loadServices(WarBasedAxisConfigurator.java:284)
at
org.apache.axis2.context.ConfigurationContextFactory.createConfigurationContext(ConfigurationContextFactory.java:82)
at
org.apache.axis2.transport.http.AxisServlet.initConfigContext(AxisServlet.java:511)
at
org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:431)
at
weblogic.servlet.internal.ServletStubImpl$ServletInitAction.run(ServletStubImpl.java:1094)
at
weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at
weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at
weblogic.servlet.internal.ServletStubImpl.createServlet(ServletStubImpl.java:970)
at
weblogic.servlet.internal.ServletStubImpl.createInstances(ServletStubImpl.java:949)
at
weblogic.servlet.internal.ServletStubImpl.prepareServlet(ServletStubImpl.java:888)
at
weblogic.servlet.internal.WebAppServletContext.preloadServlet(WebAppServletContext.java:3430)
at
weblogic.servlet.internal.WebAppServletContext.preloadServlets(WebAppServletContext.java:3375)
at
weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:3356)
at
weblogic.servlet.internal.WebAppServletContext.setStarted(WebAppServletContext.java:6208)
at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:864)
at
weblogic.j2ee.J2EEApplicationContainer.start(J2EEApplicationContainer.java:2134)
at
weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2175)
at
weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:2122)
at
weblogic.management.deploy.slave.SlaveDeployer$Application.setActivation(SlaveDeployer.java:3099)
at
weblogic.management.deploy.slave.SlaveDeployer.setActivationStateForAllApplications(SlaveDeployer.java:1768)
at
weblogic.management.deploy.slave.SlaveDeployer.resume(SlaveDeployer.java:351)
at
weblogic.management.deploy.DeploymentManagerServerLifeCycleImpl.resume(DeploymentManagerServerLifeCycleImpl.java:229)
at weblogic.t3.srvr.SubsystemManager.resume(SubsystemManager.java:136)
at weblogic.t3.srvr.T3Srvr.resume(T3Srvr.java:965)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:360)
at weblogic.Server.main(Server.java:32)
Caused by: org.apache.axis2.deployment.DeploymentException: Service [
AsynchronousResponseGenerator]
is trying to expose in a transport : <transports>
<transport>jms</transport>
</transports> and which
is not available in Axis2
at
org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:106)
at
org.apache.axis2.deployment.repository.util.ArchiveReader.buildServiceGroup(ArchiveReader.java:110)
at
org.apache.axis2.deployment.repository.util.ArchiveReader.processServiceGroup(ArchiveReader.java:144)
... 33 more
Caused by: org.apache.axis2.deployment.DeploymentException: Service [
AsynchronousResponseGenerator]
is trying to expose in a transport : <transports>
<transport>jms</transport>
</transports> and which
is not available in Axis2
at
org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:431)
at
org.apache.axis2.deployment.ServiceGroupBuilder.populateServiceGroup(ServiceGroupBuilder.java:101)
... 35 more
Caused by: org.apache.axis2.AxisFault: Service [ AsynchronousResponseGenerator]
is trying to expose in a transport : <transports>
<transport>jms</transport>
</transports> and which
is not available in Axis2
at
org.apache.axis2.deployment.ServiceBuilder.populateService(ServiceBuilder.java:341)
... 36 more
Regards,
Saurav Chatterjee
US IT DS Service Oriented Architecture (SOA)
Development Team | Saurav
Chatterjee | PriceWaterhouseCoopers
LLP | Office: +91-033-2341-3140
| Cell: +91-9830868384 | | SOA Support: 813-348-7600 |
----- Forwarded by Saurav Chatterjee/IN/M&C/PwC on 08/06/2008 05:04
PM -----
Saurav Chatterjee/IN/M&C/PwC
08/06/2008 04:03 PM
To
[email protected]
cc
Subject
Re: MDB and Axis2Link
Thanks! I am going to try this out. But I need to transport an ObjectMessage
through the JMS layer. Can it be done using Axis2?
Regards,
Saurav Chatterjee
US IT DS Service Oriented Architecture (SOA)
Development Team | Saurav
Chatterjee | PriceWaterhouseCoopers
LLP | Office: +91-033-2341-3140
| Cell: +91-9830868384 | | SOA Support: 813-348-7600 |
"sumedha rubasinghe"
<[EMAIL PROTECTED]> 08/05/2008 06:22 PM
Please respond to
[email protected]
To
[email protected]
cc
Subject
Re: MDB and Axis2
Hi,
Unless you really need the MDB, I do not see any advantage of doing so.
You can easily listen to a topic using Axis2's JMS transport [1].
Is there a specific reason / application level constraint for you to consider
MDB to listen to the topic?
/sumedha
[1] http://ws.apache.org/axis2/1_4/jms-transport.html
On Tue, Aug 5, 2008 at 6:07 PM, <[EMAIL PROTECTED]>
wrote:
All,
Anyone has any idea of how to integrate Axis2 with MDB? Here is our requirement:
1. Post a message to a topic.
2. A MDB will listen to that topic and will take appropriate actions (will
need the classes in the aar file)
Regards,
Saurav Chatterjee
US IT DS Service Oriented Architecture (SOA)
Development Team | Saurav
Chatterjee | PriceWaterhouseCoopers
LLP | Office: +91-033-2341-3140
| Cell: +91-9830868384 | | SOA Support: 813-348-7600 |
_________________________________________________________________
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged material.
Any review, retransmission, dissemination or other use of, or taking of
any action in reliance upon, this information by persons or entities other
than the intended recipient is prohibited. If you received this in error,
please contact the sender and delete the material from any computer.
_________________________________________________________________
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged material.
Any review, retransmission, dissemination or other use of, or taking of
any action in reliance upon, this information by persons or entities other
than the intended recipient is prohibited. If you received this in error,
please contact the sender and delete the material from any computer.
Your PC, mobile phone, and online services
work together like never before. See
how Windows® fits your life
_________________________________________________________________
The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you
received this in error, please contact the sender and delete the material
from any computer.
_________________________________________________________________
Reveal your inner athlete and share it with friends on Windows Live.
http://revealyourinnerathlete.windowslive.com?locale=en-us&ocid=TXT_TAGLM_WLYIA_whichathlete_us
