Thanks, James. I think that helps.
If I understand correctly, I should just use
from("jbi:service:urn:MyService") - and I get everything that folks send to
that URI. Which is the same way ServiceMix works in the first place. Sound
right?
Works for me.
Thanks.
Justin
James.Strachan wrote:
>
> On 27/11/2007, Justin Stewart <[EMAIL PROTECTED]> wrote:
>>
>> Hi, all. I'm new to Camel, and I'm using it with ServiceMix to manage
>> our
>> routing capabilities.
>> Our camel service can potentially receive messages from several other
>> services on the bus -
>> but the Camel routing examples I see always start with from(...).
>> What if I don't care where it's from - I just want to route based on
>> message
>> content?
>>
>> I'm looking also at future extensibility. I want to add new services in
>> the
>> future that will be able to send messages to this component without
>> adding
>> new from(...) cases to the service.
>>
>> Any thoughts?
>
> So the from("...") just indicates some endpoint URI that folks can
> send to. You can have multiple from clauses on a route if you want.
>
> In a JBI context; the from("...") essentially acts as the registration
> of an NMR endpoint - so that it defines a well known URI that any
> component can send to.
>
> So rather than having to change your route to include all possible
> places you want to grab messages - you could get the senders of the
> messages to just send to the same URI of your route. i.e. new services
> would just send to this single URI if you want.
>
> e.g. with a JMS hat on, a route could be based on a
> from("activemq:MyQueue") then anyone anywhere can send to the MyQueue
> to trigger the route.
>
> Does that help at all?
>
> --
> James
> -------
> http://macstrac.blogspot.com/
>
> Open Source Integration
> http://open.iona.com
>
>
--
View this message in context:
http://www.nabble.com/Origin-agnostic-routing-tf4883562s22882.html#a13978692
Sent from the Camel - Users mailing list archive at Nabble.com.
