You are viewing a plain text version of this content. The canonical link for it is here.
Posted to kandula-dev@ws.apache.org by Hannes Erven <ha...@erven.at> on 2007/09/10 19:42:56 UTC

Re: Hannes

Hi 柴华,


please keep replies on the list.


> I'm sure that i have put the client-config.wsdd file to the classpath under
> the client's axis. Then I use the eclipse to run RenterClient.java of
> the holiday example  as a java application.

There are 3 software components required for the holiday demo:

1. The Kandula Server (Coordination Server containing Kandula)
2. The Participant Server (Kandula + the Hotel and Car booking services)
3. The Client Holiday Sample GUI application.

The application (3) does use the axis libraries, but it is a standalone
application. If you use Eclipse to start it, you definitely have to add
the client-config.wsdd file to the launch configuration's classpath.

Try starting the holiday demo with "ant run" from the holiday directory,
if it succeeds there you need to modify the eclipse config.


> The kandula.properties file in the class path of this client Tomcat instance is set below:
> 
> kandula.preferredCoordinationService=http://localhost:8281/axis/services/

The important line is
kandula.localService=http://localhost:8181/axis/services/

This MUST point to the URL where other peers may reach the local
service. In the example above, this should be set to different URLs for
the three components:

1. http://coordinator.local/axis/services
2. http://hotelandcarsupplier.local/axis/services
3. value is not used

The preferredCoordinationService MUST point to the localService URL of
the Coordinator.


I suggest you try ant run to check whether it's the server or eclipse
configuration. If it is the server's config, please check the
kandula.properties files.


-hannes

---------------------------------------------------------------------
To unsubscribe, e-mail: kandula-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: kandula-dev-help@ws.apache.org