Hi josh, I am sorry, the issue that you are having is not clear to me. You could load balance within defined endpoints where you can specify the addresses of the LB endpoints as address endpoints inside synapse.xml
If you are trying to get the address from the wsa:To header to do the load balancing and it doesn't support the version of the addressing spec that you are working with, the best thing to do is to fix the synapse code. BTW: what is the specification version that you are trying to use? Please have a look at the LB sample for more information :- http://synapse.apache.org/Synapse_Samples.html Thanks, Ruwan On Fri, Feb 13, 2009 at 2:11 AM, Joshua Boverhof <[email protected]> wrote: > I'm trying to use synapse's load balancer between client and servers using > an older ws-address draft specification > > "http://schemas.xmlsoap.org/ws/2004/03/addressing"; > > So I can't use enableAddressing because the two specifications I can select > are different > > The client's messages already have the ws-address soap:headers, so I've > been able to use the property remove and set functionality to remove the > "wsa:To" header, which specifies synapse's address, and then add "wsa:To" > back in with an endpoint's URL. A single service is happy, but I can't load > balance with more than server using this solution. Hopefully there is some > other way to do this I'm not seeing but... > > since I can't place "Property", "script" or whatever mediators in the > individual load balanced endpoints I think my best option is to try to > replace the "axis2-kernel-1.4.jar" which contains "AddressingConstants". > Maybe I can build axis by hand and specify a different submission > specification... or maybe I should just hack synapse code. > > by the way I'm using globus-4.0.8 client/servers which uses the > "addressing-1.0.jar" for it's ws-addressing needs. > > thanks, > -josh -- Ruwan Linton http://wso2.org - "Oxygenating the Web Services Platform" http://ruwansblog.blogspot.com/
