Hi Matthieu

  Let me try to answer these questions inline

On 6/20/07, Matthieu Riou <[EMAIL PROTECTED]> wrote:
Hi guys,

I'm starting on the lifecycle part of the Tuscany/ODE integration to get an
engine started with all its necessary resources (transaction, persistence,
...). I can go with in-memory mode and light configuration for now but we'll
want a fully working server sooner or later. So I have a few questions:

1. How can I get server-wide configuration properties to configure the
behavior of the engine? Things like the size of our thread pool, if we
should use an embedded database or try to lookup a data source, some memory
optimization modes we can run in, ... These would be for the whole ODE
server and not on a per-process basis.

SCA does not enforce any mechanism here, I'd say you could use the
class loader to get access to the configuration file, something like :

- Add configuration file to class path (either by packaging to the sca
contribution or by adding to the class path when the jvm gets started)
and then uses classLoader.getResource() to access the file.

- You could also use a system property that points to the file.


2. How can I get the a transaction manager? I haven't been able to find an
extension point for it. If there are none available, I can still create my
own but it'd be probably be better to reuse the Tuscany one if it's there.

We don't have an extension point for transaction manager at the
moment, but if this is a requirement, we could package the geronimo
transaction manager and make it available.

3. In embedded persistence mode, ODE uses a Derby database. Which means
files located somewhere. Is there a way to lookup a given directory under
which the database could be made available? For example when we deploy ODE
in a webapp for example, the database is prepackage in the webapp and we
find it under the context root (or alternatively a path can be configured,
see 1)


Is this one database per ODE engine/server ? Then you could probably
use the approach described in item 1. I have a similar scenario in
application.data, and I'm adding the dataSource information for the
database inside the composite file, see [1], and that get's processed
by the ContributionProcessor [2].

[1] 
https://svn.apache.org/repos/asf/incubator/tuscany/java/sca/modules/implementation-data/src/test/resources/data.composite
[2] 
https://svn.apache.org/repos/asf/incubator/tuscany/java/sca/modules/implementation-data/src/main/java/org/apache/tuscany/sca/implementation/data/DATAImplementationProcessor.java

I think that's all for now but I'll certainly find more in the coming days
:)

Thanks!
Matthieu


Hope this helps, let me know if you have further questions...

--
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
http://lresende.blogspot.com/

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

Reply via email to