That looks fine. Thanks,
Ed.
On 23/05/06, Pete Robbins <[EMAIL PROTECTED]> wrote:
Ed, please take a look at the code I checked in for Jira TUSCANY-401.
There is a TuscanyRuntime class which allows you to specify the default
module and also the path to the system root. The constructor takes th
Ed, please take a look at the code I checked in for Jira TUSCANY-401.
There is a TuscanyRuntime class which allows you to specify the default
module and also the path to the system root. The constructor takes these in
the but I think it is probably better to have
these the other way round as the
Java has a TuscanyRuntime to specify the default module so I will do the
same. Something like:
TuscanyRuntime::start();
You will still need to set the TUSCANY_SCACPP_SYSTEM_ROOT to the root
deployment folder for the system.
Cheers,
On 17/05/06, Pete Robbins <[EMAIL PROTECTED]> wrote:
That's
That's a good point. A call to initialize the runtime passing the system
root and default module is a possibility. I'll look into it.
On 17/05/06, Edward Slattery <[EMAIL PROTECTED]> wrote:
I am using the tuscany c++ SCA, and am finding it quite inconvenient that
the root and default module are
I am using the tuscany c++ SCA, and am finding it quite inconvenient that
the root and default module are set by environment variables. As I use a
development environment which reads the env at startup, I have to alter
these variables , close my studio, re-open every time I want to change
tests.