You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by Hannes Erven <ha...@erven.at> on 2007/05/25 02:20:07 UTC

Re: Kandula_1 ba patch (Configuration Extension)

Hi Dasarath,


thanks for wading through the "millions" of patches currently floating 
around ;-)


Here comes another small one, and I remember discussing about it on the 
mailing list.


The patch changes the kandula.properties contents to include two URLs:

* kandula.localService=http://localhost:8181/axis/services/
  This is the address Kandula will tell any partner when handing out
  references. This should be a fixed IP address or fully qualified
  hostname (unchanged irt what is currently in SVN)

* kandula.preferredCoordinationService=http://localhost:8281/axis/services/
This is the address where Kandula will try to reach a Kandula 
activiation service to create new transaction contexts.
Why use a non-local coordination service? e.g. because you are behind a 
firewall and cannot provide the web services to your resources yourself.

* include documentation about the values to set inline in the config file.

Allowing to create transaction contexts at remote site will also 
introduce the possibility for service providers to offer transaction 
coordination services and guarantee all transaction partners a correct, 
independent and reliable coordination.
(This is perhaps more relevant in the context of WSBA).


Best regards,

	-hannes