Hi Joshua
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...
https://issues.apache.org/jira/browse/AXIS2-4211 was already opened to
get this done. I suggest we fix that to support 2004/03 without using a
workaround..
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.
Do you need this urgently for deployment into production? We could push
this into the next release of Axis2, and then inherit into Synapse..
cheers
asankha
--
Asankha C. Perera
http://adroitlogic.org
http://esbmagic.blogspot.com
