You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Simon Laws (JIRA)" <tu...@ws.apache.org> on 2007/09/25 17:16:50 UTC
[jira] Commented: (TUSCANY-1806) Support for SOAP over JMS in Axis
binding
[ https://issues.apache.org/jira/browse/TUSCANY-1806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530130 ]
Simon Laws commented on TUSCANY-1806:
-------------------------------------
Hi Dinesh
Thanks for the patch. I've just applied it to my local repo. A few small changes...
Axis2ServiceProvider
- I made all of the org.apache.axis2.description.* imports explicit
- I turned the System.out into a JDK log statement
I also added ActiveMq as a dependency of for the helloworld-ws-service sample.
Before I check it in I'd like to sort out a problem I'm having with some of the samples that use the Axis2 binding but that don't have an explicit dependency on ActiveMq. For example, helloworld-ws-service-secure. I see the following when I run this from maven (see below). So it looks like, even though this test has no JMS content, it's trying to connect to the JMS server. Looking at the trace though it's a little odd as it seems to be going down the HTTP route.
So firstly do you see this behaviour on your local setup?
Regards
Simon
Running helloworld.HelloWorldServerTestCase
25-Sep-2007 15:56:39 org.apache.axis2.deployment.DeploymentEngine loadFromClassP
ath
INFO: Module validation failed: The system is attempting to engage a module that
is not available: rampart
Server URL=http://localhost:8085/HelloWorldService
25-Sep-2007 15:56:40 org.apache.axis2.transport.jms.JMSListener handleException
SEVERE: Error connecting to JMS connection factory : QueueConnectionFactory
javax.naming.NoInitialContextException: Cannot instantiate class: org.apache.act
ivemq.jndi.ActiveMQInitialContextFactory [Root exception is java.lang.ClassNotFo
undException: org.apache.activemq.jndi.ActiveMQInitialContextFactory]
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:6
69)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:259
)
at javax.naming.InitialContext.init(InitialContext.java:235)
at javax.naming.InitialContext.<init>(InitialContext.java:209)
at org.apache.axis2.transport.jms.JMSConnectionFactory.createInitialCont
ext(JMSConnectionFactory.java:189)
at org.apache.axis2.transport.jms.JMSConnectionFactory.connect(JMSConnec
tionFactory.java:170)
at org.apache.axis2.transport.jms.JMSListener.initializeConnectionFactor
ies(JMSListener.java:253)
at org.apache.axis2.transport.jms.JMSListener.init(JMSListener.java:109)
at org.apache.axis2.engine.ListenerManager.start(ListenerManager.java:12
4)
at org.apache.axis2.transport.http.AxisServlet.init(AxisServlet.java:431
)
at org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceServlet.init(Axis
2ServiceServlet.java:69)
at org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceProvider.start(Ax
is2ServiceProvider.java:179)
at org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceBindingProvider.s
tart(Axis2ServiceBindingProvider.java:62)
at org.apache.tuscany.sca.core.assembly.CompositeActivatorImpl.start(Com
positeActivatorImpl.java:469)
at org.apache.tuscany.sca.host.embedded.impl.DefaultSCADomain.<init>(Def
aultSCADomain.java:186)
at org.apache.tuscany.sca.host.embedded.SCADomain.createNewInstance(SCAD
omain.java:231)
at org.apache.tuscany.sca.host.embedded.SCADomain.newInstance(SCADomain.
java:69)
> Support for SOAP over JMS in Axis binding
> -----------------------------------------
>
> Key: TUSCANY-1806
> URL: https://issues.apache.org/jira/browse/TUSCANY-1806
> Project: Tuscany
> Issue Type: Improvement
> Components: Java SCA Axis Binding Extension
> Affects Versions: Java-SCA-1.0, Java-SCA-1.0.1
> Reporter: dinesh shahane
> Assignee: Simon Laws
> Attachments: tuscany_1.0_binding-ws-axis2_soap_jms_TUSCANY-1806.diff
>
>
> Axis2 binding currently supports SOAP over HTTP, a simple SOAP/JMS support could be added using the Axis2 functionality. The following email thread has information about the proposed enhancements.
> http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg20760.html
> Attached patch file has support for SOAP/JMS along with samples containing service and reference. This patch modifies axis2.xml and Axis2ServiceProvider class to create a SOAP/JMS service based on specified @wsdl.port and @uri/@wsdl.binding in <binding.ws> element. Currently it doesn't support EndpointReference or extensibility elements as discussed in the email thread.
--
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: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org