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 componen
I think this makes sense, and I definately have a use for it. I've
implemented more or less the same thing at the web application level where
with a ServletContext Listener that listens for the ServletContextCreated
event and creates a SessionFactory and stores it in the application scope.
With
I've been thinking about the problem of configuring a SessionFactory for
a J2EE application where application code has no control over the system
initialization procedure. I'm thinking that instead of forcing the
application to do this programmatically, there could be a config file
like:
fa