Hendrik Jander wrote:
Hi,
thanks for the quick reply.
but this raises other questions.
please see questions inside.
Hendrik Jander wrote:
In ServiceMix, you have basically two options to make two services in
different jvm talk together:
* the first one is to go throught binding components and a known protocol
* the second one is to use a cluster flow, which ease the pain: you do
not have to define
explicitely the route from one service to the other. They are
automatically discovered.
ServiceMix uses ActiveMQ (the well known open source JMS provider) to
provide this
distribution. But it also provides load-balancing and fail-over : if
the same service is
on two different nodes, they will act as the same service and requests
may be load-balanced
how can SM know that 2 services are the same? how is this managed?
ServiceMix assumes that if two endpoints are activated with the same
information
(service qname and endpoint name), they are the same. This is currently
no versioning
of services.
between the two service instances. However, ServiceMix does not
currently provide
a service repository, where all services would automatically be deployed
on all clustered
will it one day ? :)
and when i deploy a service to one node, how do the other nodes get this to
know?
I hope, but we have not yet investigated these issues.
If you want to contribute it, fell free to do so :)
Cheers,
Guillaume Nodet
