To say the least :-) As part of setting up the RuntimeInfo for Meeraj
I am going to clean this up a little and fix 648 in the process.
I am going to refactor the command-line host so that it is similar to
the structure used by the webapp host. There will be a "standalone"
host that will allow us to boot a runtime out of an on-disk install
image structured as follows:
${tuscany.installDir}
/bin - commands typically in the form of executable jars
/boot - jars needed to boot the runtime
/extensions - composites (as jars or scdl xml files) that will
be added to the basic runtime
[[ this is the same structure that we currently have ]]
[[ why executable jars? because they are standard java and are
portable in a way shell scripts aren't ]]
Users will be able to run SCA client applications in one of two ways:
1) by adding bootstrap code to their application. They would add the
"standalone" host jar to their classpath and use an api to boot the
runtime
2) using the launcher command which will boot the runtime before
calling into the application code - booting the runtime will be
handled for them
The launcher command gives them a simple way to run SCA applications
without having code tied to Tuscany. For cases where they can't use
it (e.g. as part of a test suite), the standalone host API lets them
take control. We can provide variations on this that will work in
common environments - e.g. a variant that runs inside surefire or junit.
--
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
