On 9/20/07, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
>
> Luciano Resende wrote:
>
> > > 1. Build an ODE Interface Layer to support easy embedding. Basically
> > > you would do something like:
>
> > +1, This would be great and would allow Tuscany to use this simple
> > API, instead of creating it's own ODE EmbeddedServer. Also, should the
> > embedded server interface be flexible enough to allow injection of
> > resources already existent on the host environment (e.g TxManager,
> > etc)
>
> So conceptually similar to BSF? :-)
Mmmh what about:
class Options {
setTransactionManager(TransactionManager tm);
setDatasource(Datasource ds);
}
class Server {
init();
init(Options opt);
}
The init() with no options would of course have sensible defaults.
> would an embedded server work in the scenario where the application
> > is being deployed to an environment that already have an ODE instance
>
> Is there a reason why an Ode instance must be a singleton?
Actually not really. As far as ODE is concerned, you could have a full
server instance per process (as in BPEL process, not native process). If you
really want to have one single instance per VM I'd leave it to the client to
stick the reference to the server in whatever registry fits his needs. That
could be handled by the server itself but in a much clumsier way.
Matthieu
--- Noel
>
>
