Op 19-10-2010 10:14, Massimo Lusetti schreef:
On Mon, Oct 18, 2010 at 10:05 PM, Tom van Dijk<[email protected]> wrote:
I've made a report in JIRA, TAP5-1313.
You may expect it to be a new functionality issue for allowing extra
ModuleDef objects to be added, but the result is quite different, because I
believe dynamic services really should be in the same module that wants to
define them. Anyway, you can find it in JIRA.
The idea sounds interesting as a solution for your question (hibernate
multiple database).
Please would you like to elaborate a little more? Where is the real
evidence of dynamic? ...It's just dynamic in creation/construction
time?
Cheers
Yes, it is dynamic in construction time. Perhaps I should've named the
thing "runtime services" instead of "dynamic services" now you mention it.
The idea is not something that allows further adding/removing of
services after startup. It's just so that during startup extra services
can be defined.
Right now I'm rewriting tapestry-hibernate as an example. (and already
discovering I need an additional method in ObjectLocator,
getServices(serviceInterface, markers))
Cheers too.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
