Hi Carsten,

I just tried to reproduce your problem with the latest camel trunk and
it seemed to work for me.  This is the xml file I used:

<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans";
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
       xmlns:camel="http://activemq.apache.org/camel/schema/spring";
       xsi:schemaLocation="http://www.springframework.org/schema/beans
                http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
        http://activemq.apache.org/camel/schema/spring
                
http://activemq.apache.org/camel/schema/spring/camel-spring.xsd";>

       <bean id="sayService"
class="org.apache.camel.spring.remoting.SayService" />

       <bean id="activemq"
               class="org.apache.camel.component.jms.JmsComponent">
               <property name="connectionFactory">
                       <bean

class="org.apache.activemq.ActiveMQConnectionFactory">
                               <property name="brokerURL"

value="vm://localhost?broker.persistent=false" />
                       </bean>
               </property>
       </bean>

       <camelContext id="camel"
xmlns="http://activemq.apache.org/camel/schema/spring";>

               <proxy id="sayProxy"
                       serviceUrl="activemq:queue:test"

serviceInterface="org.apache.camel.spring.remoting.ISay"/>

               <export id="say"
                       uri="direct:say"
                       serviceRef="sayService"

serviceInterface="org.apache.camel.spring.remoting.ISay" />

               <route>
                       <from uri="activemq:queue:test" />
                       <to
uri="log:org.apache.camel.spring.remoting.service?level=DEBUG" />
                       <to uri="direct:say" />
               </route>
       </camelContext>


</beans>


And this is the Driver for the test:

import java.rmi.RemoteException;

import org.apache.camel.spring.remoting.ISay;

import org.springframework.context.support.ClassPathXmlApplicationContext;

public class Main {
    public static void main(String[] args) throws RemoteException,
InterruptedException {
        ClassPathXmlApplicationContext ctx = new
ClassPathXmlApplicationContext("test.xml");
        ctx.start();

        ISay say = (ISay)ctx.getBean("sayProxy");

        System.out.println("Calling service..");
        say.say();
        System.out.println("Service call done.");

        ctx.stop();
    }
}


Everything looked ok to me.

On Jan 10, 2008 7:13 AM, Carsten Krebs <[EMAIL PROTECTED]> wrote:
>
> Ooops, it was something like that...
> The queue names on the client and remote side differed.
> Now this simple example works fine, but now I'm getting the same
> TimeoutException in the moment I'm trying to route the incoming message on
> the remote side. Routing the message on the client side works fine.
>
> If I use the following camel context
>
>         <camelContext id="camel"
>                 xmlns="http://activemq.apache.org/camel/schema/spring";>
>
>                 <export id="say"
>                         uri="direct:say"
>                         serviceRef="sayService"
>                         
> serviceInterface="org.apache.camel.spring.remoting.ISay" />
>
>                 <route>
>                         <from 
> uri="activemq:queue:org.apache.camel.spring.remoting.ISay" />
>                         <to 
> uri="log:org.apache.camel.spring.remoting.service?level=DEBUG" />
>                         <to uri="direct:say" />
>                 </route>
>         </camelContext>
>
> I'm getting the TimeoutException, in contrast the following camel context
> works fine:
>
>         <camelContext id="camel"
>                 xmlns="http://activemq.apache.org/camel/schema/spring";>
>
>                 <export id="say"
>                         
> uri="activemq:queue:org.apache.camel.spring.remoting.ISay"
>                         serviceRef="sayService"
>                         
> serviceInterface="org.apache.camel.spring.remoting.ISay" />
>         </camelContext>
>
> Regards,
>
> Carsten
>
>
>
> James.Strachan wrote:
> >
> >
> > It looks like there's a timeout there; I wonder is the server side
> > running?
> >
> >
>
> --
> View this message in context: 
> http://www.nabble.com/spring-remoting-over-jms-tp14640388s22882p14731185.html
>
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>



-- 
Regards,
Hiram

Blog: http://hiramchirino.com

Open Source SOA
http://open.iona.com

Reply via email to