I expressed this badly, of course. I was meaning to imply no hooks into the system initialization procedure as opposed to hooks into the component _instance_ initialization procedure. You want to configure a single session factory thats shared between potentially many instances of several components (whether these components be servlets or enterprise beans). I think its reasonable to try and make that a bit easier for people.
P.S. Does anyone here use Avalon. I've been having a look at their stuff lately and kind of like it and I'm wondering about writing an adapter that exposes hibernate as an Avalon component. But I've never used Avalon so I would probably not get it right on my own...... > While I don't necessarily think this is a bad idea, I'm not sure I > quite understand why you say a J2EE app has no control over > initialization. What particular app model(s) did you have in mind here? > WAR's for servlet engines? EJB apps? other server side models? _______________________________________________________________ Sponsored by: ThinkGeek at http://www.ThinkGeek.com/ _______________________________________________ Hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
