On Dec 31, 2009, at 6:12 PM, Evgeny Ryabitskiy wrote:
> One more thing... is DI container would be replaceable by some
> other... like Spring or it' will be solid-embedded?
The goal of the current design is to make it mostly invisible to the
rest of the application and non-conflicting with the existing user
preferred DI mechanism. Take a look at
org.apache.cayenne.runtime.ServerRuntime. It completely encapsulates
the DI Injector instance. So you can keep using Spring in your app if
you were doing it already, without concerning yourself about Cayenne
DI. It will manage all Cayenne built-in "services" internally, but it
won't attempt injecting anything in the application classes. For that
you can use Spring if you choose so.
The only case when a user will interact with the container is to
configure Cayenne (e.g. to override some Cayenne standard service).
Even that can be bridged with Spring - you may start CayenneRuntime
via Spring, passing all needed configuration via custom modules.
Andrus
This archive was generated by hypermail 2.0.0 : Thu Dec 31 2009 - 11:45:29 EST