You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by jep <ws...@gmail.com> on 2006/11/13 08:48:20 UTC
jmsFlow component addressing
when using jmsFlow, is it possible to prevent certain components from being
clustered? i want to be able to address components (that exist in a number
of clustered containers) relative to their container without having to give
them unique endpoints.
--
View this message in context: http://www.nabble.com/jmsFlow-component-addressing-tf2620581s12049.html#a7312674
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: jmsFlow component addressing
Posted by Christian Schneider <ch...@die-schneider.net>.
I am searching for the same thing for our SOA. We want to establish
several Business Domains.
Inside the domains communication should be possible without further
policies. Between the domains only public services should be reachable.
Eventually there will
also be a layering of business domains and you have to go through the
layers.
A possibility would be to change JMSFlow so it executes your policies.
It would then be possible to
have complete location transparency and special policies. I think this
could be an interesting solution.
Simply look into the code of JMSFlow it is quite small and easy to
understand.
Christian
jep schrieb:
> when using jmsFlow, is it possible to prevent certain components from being
> clustered? i want to be able to address components (that exist in a number
> of clustered containers) relative to their container without having to give
> them unique endpoints.
>
--
Christian Schneider
---
http://www.liquid-reality.de
Re: jmsFlow component addressing
Posted by jep <ws...@gmail.com>.
Never mind that, found http://issues.apache.org/activemq/browse/SM-510
SM-510 .
jep wrote:
>
> thanks, in my case i think i'm better of using jms binding for the
> addressing and leaving the flows unclustered.
>
> is there a way to have message properties transported when using
> servicemix-jms?
>
>
> gnodet wrote:
>>
>> The main point when using jms or jca flow is that two jbi endpoints
>> activated with the same service name / endpoint name are considered
>> as a unique endpoint, with load-balancing between them. If you do not
>> want this behavior, you need to give them different names, as direct
>> jbi endpoint addressing is not supported by these flows.
>>
>> On 11/13/06, jep <ws...@gmail.com> wrote:
>>>
>>> when using jmsFlow, is it possible to prevent certain components from
>>> being
>>> clustered? i want to be able to address components (that exist in a
>>> number
>>> of clustered containers) relative to their container without having to
>>> give
>>> them unique endpoints.
>>> --
>>> View this message in context:
>>> http://www.nabble.com/jmsFlow-component-addressing-tf2620581s12049.html#a7312674
>>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>>
>>>
>>
>>
>> --
>> Cheers,
>> Guillaume Nodet
>>
>>
>
>
--
View this message in context: http://www.nabble.com/jmsFlow-component-addressing-tf2620581s12049.html#a7333020
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: jmsFlow component addressing
Posted by jep <ws...@gmail.com>.
thanks, in my case i think i'm better of using jms binding for the addressing
and leaving the flows unclustered.
is there a way to have message properties transported when using
servicemix-jms?
gnodet wrote:
>
> The main point when using jms or jca flow is that two jbi endpoints
> activated with the same service name / endpoint name are considered
> as a unique endpoint, with load-balancing between them. If you do not
> want this behavior, you need to give them different names, as direct
> jbi endpoint addressing is not supported by these flows.
>
> On 11/13/06, jep <ws...@gmail.com> wrote:
>>
>> when using jmsFlow, is it possible to prevent certain components from
>> being
>> clustered? i want to be able to address components (that exist in a
>> number
>> of clustered containers) relative to their container without having to
>> give
>> them unique endpoints.
>> --
>> View this message in context:
>> http://www.nabble.com/jmsFlow-component-addressing-tf2620581s12049.html#a7312674
>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>
>>
>
>
> --
> Cheers,
> Guillaume Nodet
>
>
--
View this message in context: http://www.nabble.com/jmsFlow-component-addressing-tf2620581s12049.html#a7332696
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: jmsFlow component addressing
Posted by Guillaume Nodet <gn...@gmail.com>.
The main point when using jms or jca flow is that two jbi endpoints
activated with the same service name / endpoint name are considered
as a unique endpoint, with load-balancing between them. If you do not
want this behavior, you need to give them different names, as direct
jbi endpoint addressing is not supported by these flows.
On 11/13/06, jep <ws...@gmail.com> wrote:
>
> when using jmsFlow, is it possible to prevent certain components from being
> clustered? i want to be able to address components (that exist in a number
> of clustered containers) relative to their container without having to give
> them unique endpoints.
> --
> View this message in context: http://www.nabble.com/jmsFlow-component-addressing-tf2620581s12049.html#a7312674
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
>
--
Cheers,
Guillaume Nodet