Hi Daniel Some comments in line....
Regards Simon [1] http://svn.apache.org/repos/asf/incubator/tuscany/java/sca/modules/node2-launcher/src/main/java/org/apache/tuscany/sca/node/launcher/NodeLauncherUtil.java On Thu, Apr 10, 2008 at 4:37 PM, <[EMAIL PROTECTED]> wrote: > Hi Simon, > > My colleague Jürgen and I did some further testing using the same codebase > (upodated today): > > - he used mvn -Peclipse eclipse:eclipse to create the eclipse project > - I set up the eclipse project manually > > His project runs fine, mine has the known issues. The only difference in > both projects is the classpath > - the mvn generated project uses project references and jars > - my project uses the Tuscany lib (that means every jar in > \tuscany-sca-1.2-incubating-SNAPSHOT\lib) > > Any ideas what could be wrong using the lib? Ah - That's a good piece of detective work. The new workspace support uses some new modules, e.g, node2-* that are intended in due course to replace some of the existing modules and this may be causing problems with the whole lib dir in the classpath. Are you able to manually pull out the correct dependencies and try that. I should point out that there is also some code in the launcher we are using that calculates the classpath at runtime. See the runtimeClassLoader method in [1]. This uses the location of the launcher jar to identify the directory of other jars that need loading. So if you look in the ant script use to run this from the binary distribution (build.xml) you will see that the classpath is very short. This is because the code takes this classpath and automatically appends all of the runtime jars. The important thing is that the stated node2 jars come first. While this runtime classpath creation won't work from eclipse (because the modules & lib dirs are not in the right place) you may be able to play the trick of putting the node2 jars first on your classpath. > > ---- > > For a better understanding, could you please elaborate on the files > workspace.xml. domain.composite and cloud.composite ? > What are the differences and what are the files used for? Sure. workspace.xml - indicates the ID and location of each contributions that has been added to the domain. domain.composite - the virtual domain composite. This is an SCA composite that represents the virtual domain which includes all of the composites that will run in the domain. A URI is provided which indicates which contribution each composite comes from. Ultimately an SCANode2 instance will be started for each composite included in the virtual domain. Each SCANode2 instance can be running on separate/distributed processors. So the virtual domain is a consolidated description of you distributed SCA application cloud.composite - describes the compute cloud (the set of distributed SCANode2 instances) being used to run the SCA application. Each node is assigned a composite and also has details of the configuration of bindings when they run on that node, for example, the root URI is set. It's possibly slightly confusing that this file is in SCA composite format also but this is a convenience because firstly we didn't have to create a new file format and secondly there may be some benefit in the future of representing this network of nodes as a network of SCA services for management purposes although we don't do that yet. These three files come pre-loaded for this sample but they are the files that hold all of the state behind the workspace admin app. > > Can the calculator sample already be used for failover (e.g. by starting > multiple instances of LaunchCalculatorNodeC) or is failover only running in > your local sandbox? I believe that I should be able to get load balancing working fairly easily (famous last words!) and as the calculator services are stateless this will provide failover too. Failover of stateful services will not work yet and will take more effort to investigate and implement a solution. > > Thanks a lot. > > Bye, > Daniel > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
