Why not use the ActiveMQ component rather than the Spring Event
component? The spring event component only works inside a single JVM
(as thats what spring events are designed for)?
2008/10/17 cmoulliard <[EMAIL PROTECTED]>:
>
> James,
>
> My question is in relation with the spring event component.
>
> Client : java web application server designed as an AJAX application and
> using cometd/bayeux technology to provide push mechanism from web server to
> the browser client. From the web site, the client can call a service "track
> a parcel" who will register the client HTTP request + sessionId + parcel to
> be followed) into a tracker event service (=subscription).
>
> Server : A camel bus runs in // and subscribe to the events (of the tracker
> event service) for which the status of the parcel must be provided. For each
> event (1 event corresponds to one client HTTP request and one parcel id), it
> will call different process on a regular basis (by example triggered by
> quartz) :
>
> from("quartz:every 10 minutes")
> .to("event://track") <-- fetch events for which we have to check the status
> .to("bean:checkStatus")
>
> If a parcel has been delivered and its status is equal to "deliver", then
> camel must raise an event to inform back the event listener of the web
> application server. The client having a subscription to this event will be
> notified back '(= push) in its browser (through AJAX & JSON) that its parcel
> has been delivered.
>
> KR,
>
> Charles
>
>
>
> James.Strachan wrote:
>>
>> 2008/10/17 cmoulliard <[EMAIL PROTECTED]>:
>>>
>>> Hi,
>>>
>>> I would like to know if it is possible to work in a client-server mode
>>> with
>>> Camel ?
>>> I launch a camelcontext in a standalone mode using a spring-camel.xml
>>> file
>>> using the following code :
>>>
>>> public class CamelServer {
>>>
>>> /**
>>> * Start Camel context.
>>> *
>>> * @param args
>>> * the args
>>> */
>>> public static void main(String[] args) {
>>>
>>> Main starter = new Main();
>>> // starter.enableDebug();
>>> // starter.enableTrace();
>>>
>>>
>>> starter.setApplicationContextUri("com/xpectis/test/ProcessEvent-context.xml");
>>>
>>> starter.run(args);
>>> }
>>>
>>> }
>>>
>>> From another java client that I call "camel client", I would like to
>>> communicate with the endpoints of my camelContext in order to
>>> produce/consume messages.
>>>
>>> How can I achieve this ?
>>
>> What kind of endpoints are they? It kinda depends on technology.
>>
>> e.g. for JMS endpoints, they are already client-server; you send to a
>> queue on the client and the server can receive it etc.
>>
>> If you have SEDA or in JVM endpoints in the server you can bridge from
>> some kind of remoting technology (file/http/jms/JPA/whatever) to your
>> local in JVM endpoints in the
>> server.
>>
>> Or you could use Spring Remoting to invoke arbirary beans in the
>> server over some transport...
>> http://activemq.apache.org/camel/spring-remoting.html
>>
>>
>> Could you give more of an idea of the kind of thing you mean?
>> --
>> James
>> -------
>> http://macstrac.blogspot.com/
>>
>> Open Source Integration
>> http://fusesource.com/
>>
>>
>
>
> -----
> Enterprise Architect
>
> Xpectis
> 12, route d'Esch
> L-1470 Luxembourg
>
> Phone +352 25 10 70 470
> Mobile +352 621 45 36 22
>
> e-mail : [EMAIL PROTECTED]
> web site : www.xpectis.com www.xpectis.com
> My Blog : http://cmoulliard.blogspot.com/ http://cmoulliard.blogspot.com/
> --
> View this message in context:
> http://www.nabble.com/Can-we-work-in-a-client-server-mode-with-Camel---tp20033318s22882p20034398.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
--
James
-------
http://macstrac.blogspot.com/
Open Source Integration
http://fusesource.com/
