Warning ... reply
Alexandros Paramythis wrote:
(Note: The way in which I envisaged using the extensions,
is to create one that must then be used for all components
that need to "collect" persistence configuration information;
the collected information would then somehow be fed into the
initialization of Hibernate)
Thinking ....
Given that your looking at an embeded scenario - there are a bunch of options open to you. One of these is to get the root metamodel and go though the model harvesting the info about components that need persistence, and programatically contruct the configuration for the persistence component. You could then set the configuration for the persistence component programatically before deploying the root container.
Cheers, Stephen.
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/ | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
