I made this change for the launcher and plan to make a similar change for the server code shortly.

The name of the profile can be overridden by setting the "tuscany.profile" system property - the default value for this is "launcher" The root for each profile defaults to "$ {tuscany.installDir}/profiles/${tuscany.profile}" and again can be overridden by specifying a system property with the name "tuscany.profileDir.${tuscany.profile}"

I moved "runtime.properties" from etc to the profile's root directory for simplicity as in many cases a profile may just contain it and the system scdl. I made properties loaded from this file available through the RuntimeInfo service (backed by default values from the system properties). Configuration values for the runtime itself (such as the location of the system scdl or the implementation class) can be specified in this file on a per-profile basis.

--
Jeremy

On Jan 4, 2007, at 7:12 AM, Jeremy Boynes wrote:

One problem we had with M2 was that the launcher used a single set of extensions for every application it ran. I think Meeraj's server config will have a similar issue with it's ability to run multiple runtimes at the same time (with the likelihood that the reason someone wants to do that would be that they are configured differently).

To address this, I am going to convert the standalone distro to support the notion of runtime profiles by adding a "profiles" directory in the root containing a subdirectory for each profile. There will be two built-in profiles "launcher" and "server" present by default and used by the launcher and server commands. Each profile will contain an "etc" directory which would contain the "runtime.properties" and "system.scdl" files used by that profile's runtime. As a side benefit moving the system.scdl out of the launcher jar will make it easier for users to change it if they want.

I'll also add support for a new command line option ( - Dprofile=... ) to allow the user to override the default profile for each command.

--
Jeremy


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to