I've been doing some hacking on Rick's launcher and it is now capable
of booting both system and application composites.
I've tweaked the eagerinit sample so that it can now be run using the
launcher from a clean distribution. The sandbox build automatically
puts a distribution in your local maven repository. To install it, do
something like:
$ mkdir /tmp/tuscany
$ cd /tmp/tuscany
$ jar xf ~/.m2/repository/org/apache/tuscany/standalone/1.0-sandbox-
SNAPSHOT/standalone-1.0-sandbox-SNAPSHOT-bin.zip
To run the eagerinit sample
$ java -jar bin/launcher.jar --classpath ~/.m2/repository/org/apache/
tuscany/samples/sca/sample-eagerinit/1.0-sandbox-SNAPSHOT/sample-
eagerinit-1.0-sandbox-SNAPSHOT.jar
The launcher is a small jar that will do all the initialization of
the Tuscany runtime for you - there's no longer any need to add
Tuscany stuff to the classpath or have the application create a
TuscanyRuntime. The only SCA dependency that your code may need is on
the spec APIs (if you use them).
Under the covers, the launcher boots a default runtime configuration
based on the jars found in the "boot" directory in the distro. It
reads a "system.scdl" composite definition from META-INF/tuscany to
determine what that configuration looks like. That's hard coded at
the moment; we need to make it configurable.
Once the runtime is running, it loads the application configuration
from a "default.scdl" composite located in META-INF/sca and then
calls the main() method from the application jar. You can also
specify the main class on the command line with the --main option
rather than adding it to the manifest.
--
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
