Return-Path: 
 <axis-dev-return-58332-apmail-ws-axis-dev-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-axis-dev-archive@www.apache.org
Received: (qmail 64462 invoked from network); 22 Mar 2007 17:05:40 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 22 Mar 2007 17:05:40 -0000
Received: (qmail 70531 invoked by uid 500); 22 Mar 2007 17:05:43 -0000
Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org
Received: (qmail 70493 invoked by uid 500); 22 Mar 2007 17:05:43 -0000
Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
list-help: <mailto:axis-dev-help@ws.apache.org>
list-unsubscribe: <mailto:axis-dev-unsubscribe@ws.apache.org>
List-Post: <mailto:axis-dev@ws.apache.org>
List-Id: <axis-dev.ws.apache.org>
Delivered-To: mailing list axis-dev@ws.apache.org
Received: (qmail 70482 invoked by uid 99); 22 Mar 2007 17:05:43 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Mar 2007 10:05:43 -0700
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (herse.apache.org: domain of lists@nabble.com designates
 72.21.53.35 as permitted sender)
Received: from [72.21.53.35] (HELO talk.nabble.com) (72.21.53.35)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Mar 2007 10:05:34 -0700
Received: from [72.21.53.38] (helo=jubjub.nabble.com)
	by talk.nabble.com with esmtp (Exim 4.50)
	id 1HUQit-000229-LU
	for axis-dev@ws.apache.org; Thu, 22 Mar 2007 10:05:11 -0700
Message-ID: <9619485.post@talk.nabble.com>
Date: Thu, 22 Mar 2007 10:05:11 -0700 (PDT)
From: badrys <khaled.badri@gmail.com>
To: axis-dev@ws.apache.org
Subject: Re: Axis2 SOAP-over-JMS
In-Reply-To: <4602B225.501@wso2.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Nabble-From: khaled.badri@gmail.com
References: <9550011.post@talk.nabble.com> <45FED768.6010503@wso2.com>
 <9567946.post@talk.nabble.com> <45FFA2F3.8000200@wso2.com>
 <9590759.post@talk.nabble.com> <460128BA.4040108@wso2.com>
 <9594057.post@talk.nabble.com> <46015F6B.3030300@wso2.com>
 <9615926.post@talk.nabble.com> <4602B225.501@wso2.com>
X-Virus-Checked: Checked by ClamAV on apache.org


Actually, I understood the "Version" thing : Version  is the web service
sample given with Axis2 and according to the Apache documentation
(http://ws.apache.org/axis2/1_1/jms-transport.html), when the JMS transport
starts it checks all the destinations specified by all the web services and
gives a default destination name (which is the same as the name of the
service) to those who doesn't specify one. Since "Version" is one of them,
the JMS transport associate a destination named Version to it.
But my real problem now is the "Axis Fault : Operation Not Found" thing :
when I checked this url :
"http://localhost:8080/axis2/services/MyService/myOperation" I found this:

<soapenv:Fault>
   <faultcode>soapenv:Client</faultcode>	
   <faultstring>
         Service Not found EPR is
/axis2/services/HelloPublishSubscribe/echoHello
   </faultstring>
   <detail/>
</soapenv:Fault>

I guess it means that Axis2 doesn't recognize my web service's operation but
I don't know what caused that, and what is really weird : on the url :
"http://localhost:8080/axis2/services/" , I can see my web service and its
operations displayed.
can you help me with this issue ?

Thanks for your time.



asankha wrote:
> 
> 
> 
> 
>   
> 
> 
> Are you using the latest trunk? there was a defect when the JMS
> Destination name was different from its JNDI name but I am not sure if
> this is the case. If the JMS transport creates a new Queue with the
> name "Version", then obviously it cannot find a JMS destination with
> the name "Version" on the JNDI context you specify.. Could you check
> why that might be? 
> 
> asankha 
> 
> badrys wrote:
> 
>   Hi Asankha
> 
> When I deployed my web service (the publish/subscirbe application I told
> you
> about before). Axis2 generated a wsdl and the wsdl2java tool generated a
> code (stub and callback handler) that I used to create a client. 
> However, I noticed something weird when launching Axis2 : although I
> didn't
> forget to specify my destination (topic) and launch my JMS Broker before
> that, It put this on the terminal:
> 
> [CODE]
> ATTENTION: Cannot find destination : Version Creating a Queue with this
> name
> 22 mars 2007 15:06:28 org.apache.axis2.transport.jms.JMSConnectionFactory
> listen
> 
> INFO: Connection factory : default initialized...
> 22 mars 2007 15:06:28 org.apache.axis2.transport.SimpleAxis2Server main
> INFO: [SimpleAxisServer] Started
> [/CODE]
> 
> And when I try to execute my client, axis2 came up with this exception :
> 
> [CODE] 
>  22 mars 2007 15:07:46
> org.apache.axis2.transport.jms.JMSMessageReceiver$Worker r
> un
> GRAVE: JMS Worker [JMSWorker-1] Encountered an Axis Fault : Operation Not
> found
> EPR is  and WSA Action =  urn:runSubscriber
> org.apache.axis2.AxisFault: Operation Not found EPR is  and WSA Action = 
> urn:ru
> nSubscriber
>         at
> org.apache.axis2.engine.DispatchPhase.checkPostConditions(DispatchPha
> se.java:48)
>         at org.apache.axis2.engine.Phase.invoke(Phase.java:398)
>         at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:522)
>         at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:487)
>         at
> org.apache.axis2.transport.jms.JMSMessageReceiver$Worker.run(JMSMessa
> geReceiver.java:198)
>         at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Wor
> ker.runTask(ThreadPoolExecutor.java:650)
>         at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Wor
> ker.run(ThreadPoolExecutor.java:675)
>         at java.lang.Thread.run(Thread.java:595)
> [/CODE]
> 
> Have you any idea of what is causing this ?
> 
> Many thanks.
> badrys
>  
> 
> asankha wrote:
>   
>   
>     Hi Badrys
>     
>     
>       does the fact of specifying a JMS destination in
> services.xml create a physical Destination (a Java Object that I can
> access
> from a java code) ?  and if it's the case can you tell me how to do it ?
>   
>       
>     
>     Yes, if your JMS provider supports this. (e.g. ActiveMQ) This would 
> create a JMS Queue with a name same as that of the service, and you 
> should be able to access this using JNDI from Javacode outside
> 
> asankha
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org 
> For additional commands, e-mail: axis-dev-help@ws.apache.org 
> 
> 
> 
>     
>   
>   
>   
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Axis2-SOAP-over-JMS-tf3426346.html#a9619485
Sent from the Axis - Dev mailing list archive at Nabble.com.


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