> Oh, looking back at your original code, it seems like Tomcat lets you > bind a Reference to an ObjectFactory in the webapp.xml. This is > tomcat-specific stuff, by the looks. > > Oh, now I remember! Tomcat has a read-only JNDI server, doesn't it? That > is why you had trouble? Why don't you just get a real JNDI > implementation instead?
Well, I'm open to suggestions, but there are alot of people using plain old Tomcat and it'd be nice if this stuff just worked with Tomcat & Hibernate & JNDI. If I recast my code into something mroe like an extended version of the JndiSessionFactoryImpl example (except that name is off, the class is an impl of ObjectFactory not SessionFactory), then would you consider adding to Hibernate so Tomcat "just works"? Perhaps calling the class TomcatSessionFactoryObjectFactory or SessionFactoryTomcatObjectFactory. It's getObjectInstance() would first call SessionFactoryObjectFactory.getObjectInstance() and if that returns null, do the Configuration stuff and finally call Configuration.buildSession(). Either way, I will contribute comments/docs to page 114. John Allison [EMAIL PROTECTED] ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
