A few comments:
1) Our distribution already contains the manifest.jar and equinox-manifest.jar:
* manifest.jar has the Main-Class set to the node launcher and Class-Path
set to the required Tuscany modules and 3rd party jars
* equinox-manifest.jar has the Mani-Class set to the equinox node launcher
and Class-Path set to the dependent jars for the launcher itself without
pulling other Tuscany modules and 3rd party jars which are bundles under OSGi.
We also have the configuration generated to list the bundles. It can be pointed
using -Dosgi.configuration.area (system property).
I suggest that our tuscany.bat to leverage that instead of using the
osgi.config and default.config which require manual maintenance and **
classpath drags unnecessary jars.
2) Let's use -<option> instead of positional arguments. For example,
tuscany -osgi contrib
3) We should allow the deployment composite to be used to launch the node, for
example
tuscany -composite <compositeURI> contrib1 contrib2 ... contribN
The compositeURI can be a relative URI in one of the contribs or an absolute
URI which points to an external composite file.
4) Do we prefer to have multiple commands for different purposes or one command
with different options?
Thanks,
Raymond
From: ant elder
Sent: Thursday, January 29, 2009 6:33 AM
To: [email protected]
Subject: Re: svn commit: r737681 - /tuscany/java/sca/samples/build-common.xml
[snip]
Ok I shall start, feel free to help. We need:
- some samples changed to have the very simple Ant build scripts
- a launcher as in TUSCANY-2789
- a launcher config file for the JSE runtime
- a launcher config file for the equinox runtime
- a Windows .bat file that calls java -jar launcher.jar
- a shell script .sh file that calls java -jar launcher.jar
- update the distribution to have a bin/ folder containing the launcher bits
...ant
Ok the launcher part of this is working now. Build the all distribution and
that will have a new bin/ folder which has a launcher.jar, config files for JSE
and OSGi, and a tuscany.bat.
You can run that with java -jar or directly executing the .bat but easiest is
to add the bin/ folder to your PATH by doing something like "set
PATH=%PATH%;\Tuscany\distros\tuscany-sca-2.0-SNAPSHOT\bin" and then you just
need to type "tuscany" to runt the samples. For example in the
tuscany-sca-2.0-SNAPSHOT\samples\implementation-java-calculator folder type:
tuscany target\sample-implementation-java-calculator.jar
or to run it in the OSGi runtime use:
tuscany osgi target\sample-implementation-java-calculator.jar
Use "tuscany /?" for some brief help - If you use "debug" as the first
parameter it lets you use connect a remote Java debugger to the runtime. If you
use "fork" then it starts a new command prompt to run the sample which can be
useful for the samples which have separate service and reference parts.
...ant
To make that easier to try without needing to do a build i've published the
binary distro snapshot at:
http://people.apache.org/repo/m2-snapshot-repository/org/apache/tuscany/sca/tuscany-distribution-all/2.0-SNAPSHOT/tuscany-distribution-all-2.0-20090129.140350-1-bin.zip
...ant
