were u thinking of leaving the option to configure programmatically in?
the option to configure by file would definitely be usefull in some
circumstances. most people r probably aware of the problems with this
in the following scenario, but i'll babble on about it anyway. when
deploying an appl
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
