>From what you are describing, there is a lot going on behind the scenes to provide the right URI to use based on multiple criterias. Have you thought about using something like a IP Sprayer to handle the load balancing and high availability of your service and use the IP Sprayer URI as constant URI ?
On Tue, Jun 24, 2008 at 2:45 PM, Dean H Mitchell <[EMAIL PROTECTED]> wrote: > Hi- > > One of my components is implemented as a distributed web service under > Tomcat/Axis2. Currently the IP address of this service is hardcoded in my > .composite XML file passed to SCADomain.newInstance. A problem we're trying > to figure out is how to handle this when that IP address has to change? It > might change for a number of reasons..the original machine is down and > another has to fulfill the request, load balancing, or because of some other > routing criteria we might employ. Is there any clean way in SCA to handle > this? E.g. handling dynamic IP addresses in the composite file? The only > options I've come up with are a bit of a hack...programmatically altering > the XML composite file with the new IP address before loading it in, or > traversing the Component/ComponentReference/Binding lists post-load and > finding the proper binding and doing a setURI with the new IP. > > thanks, > Dean. > -- Luciano Resende Apache Tuscany Committer http://people.apache.org/~lresende http://lresende.blogspot.com/
