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 datasource, some memory optimization modes we can run in, ... These would be for the whole ODE server and not on a per-process basis. 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. 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) I think that's all for now but I'll certainly find more in the coming days :) Thanks! Matthieu
