Sergey Thanks for your quick response and sharing these two approaches . To me it looks like this approach will work if the web service consumer is running inside same container . Unfortunately client for my services is application running on force.com . So the load balancing and fail over has to be something outside and supported by container .
I am thinking of implementing a Proxy service as a plain cxf web service (Not OSGI Service) . This Proxy service can then go to service registry , get the list of available services and then execute the local service or service from other node to support fail over. The proxy service will be exposed on HTTP port (and not on osgi-http port on jboss) and therefore can be load balanced by the Jboss AS 7 Web container. I also read blog by David Bosschaert http://coderthoughts.blogspot.com/2009/02/distributed-osgi-simple-example.html. In one of the response he said "A service has arbitrary map of properties associated with it ." These properties can be passed to the ServiceTracker as a filter for selecting a service when same service is registered/listed in service registry multiple times. " A service could publish* (and periodically update) *a property which advertises its load and the load balancer could automatically select the service with the lowest load" Question is I know how to set the properties on service during registration . But how do I update these properties ? Thanks Sunil -- View this message in context: http://cxf.547215.n5.nabble.com/DOSGI-Service-load-balancing-tp5713383p5713402.html Sent from the cxf-user mailing list archive at Nabble.com.
