Re: Soap Over JMS using Embedded Axis2 Engine

Ali Sadik Kumlali Tue, 02 Jan 2007 14:56:56 -0800

Hi Ted,

War distribution(AxisServlet actually) doesn't initialize JMS listener. Please 
look at followings:
1) http://www.mail-archive.com/axis-user@ws.apache.org/msg21464.html
2) https://issues.apache.org/jira/browse/AXIS2-1488

Regards,

Ali Sadik Kumlali

----- Original Message ----
From: Ted Jones <[EMAIL PROTECTED]>
To: axis-user@ws.apache.org; [EMAIL PROTECTED]
Sent: Tuesday, January 2, 2007 9:35:14 PM
Subject: RE: Soap Over JMS using Embedded Axis2 Engine

 _filtered {
font-family:Tahoma;
}
 _filtered {margin:1.0in 1.25in 1.0in 1.25in;}
P.MsoNormal {
FONT-SIZE:12pt;MARGIN:0in 0in 0pt;FONT-FAMILY:"Times New Roman";}
LI.MsoNormal {
FONT-SIZE:12pt;MARGIN:0in 0in 0pt;FONT-FAMILY:"Times New Roman";}
DIV.MsoNormal {
FONT-SIZE:12pt;MARGIN:0in 0in 0pt;FONT-FAMILY:"Times New Roman";}
A:link {
COLOR:blue;TEXT-DECORATION:underline;}
SPAN.MsoHyperlink {
COLOR:blue;TEXT-DECORATION:underline;}
A:visited {
COLOR:purple;TEXT-DECORATION:underline;}
SPAN.MsoHyperlinkFollowed {
COLOR:purple;TEXT-DECORATION:underline;}
SPAN.EmailStyle17 {
COLOR:navy;FONT-FAMILY:Arial;}
DIV.Section1 {
}

Thanks for the reply Brennan. I believe I have everything 
configured as per the link below, but I keep timing out while "waiting for the 
server to send the response".

I am seeing this in my ActiveMQ 
console: myservice - No subscriptions registered, will not dispatch 
message at this time.

"myservice" is the destination I am dynamically adding in 
my client code and that matches with the destination in my 
services.xml.

Here is my services.xml:

<service name="service">

<description>
        My Web 
Service

</description>
 <transports>

<transport>jms</transport>

</transports>
    <parameter name="ServiceClass" 
locked="false">com.test.soap.lds.service.DataServiceWebService</parameter>
 <parameter 
name="allowedMethods" 
locked="false">executeDataservice</parameter>    

 <parameter name="transport.jms.ConnectionFactory" 
locked="true">QueueConnectionFactory</parameter>

<parameter name="transport.jms.Destination" 
locked="true">myservice</parameter> 

<messageReceivers>
      <messageReceiver 
mep="http://www.w3.org/2004/08/wsdl/in-only";

class="org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver"/>

<messageReceiver mep="http://www.w3.org/2004/08/wsdl/in-out";

class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/>

</messageReceivers>
</service>

Thanks for your help,

Ted

From: Brennan Spies 
[mailto:[EMAIL PROTECTED] 
Sent: Friday, December 29, 2006 
10:19 PM
To: axis-user@ws.apache.org
Subject: RE: Soap Over 
JMS using Embedded Axis2 Engine

Ted,

Did you 
uncomment/configure the appropriate entries in your axis2.xml as well as your 
.aar’s service.xml?

http://ws.apache.org/axis2/1_1/jms-transport.html

From: Ted Jones 
[mailto:[EMAIL PROTECTED] 
Sent: Friday, December 29, 2006 3:36 
PM
To:
 axis-user@ws.apache.org
Subject: Soap Over JMS using Embedded Axis2 
Engine

I am attempting to execute a web 
service via ActiveMQ. The web service is deployed to an Axis2 engine that is 
embedded in a web app running on Tomcat 5.5. Are there any known *gotchas* 
here? 
I cannot seem to communicate with the service via JMS as it keeps timing 
out. When I change my endpoint in the client call from the JMS endpoint to the 
web service endpoint, it finds it.

Thanks,

Ted

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com

Re: Soap Over JMS using Embedded Axis2 Engine

Reply via email to