> I'm afraid that I have to say your reading of the JNDI spec is mistaken. Fair enough, could be.
> Keep > reading further down into that JavaDoc, where it makes quite clear that the > ObjectFactory is responsible for creating objects for References that were > /already bound to a name/, ie. exactly how Hibernate is doing it now. > I have never construed ObjectFactory as having responsibility for creating > completely new objects for unbound names. But that's exactly what the other ObjectFactorys I've seen do. The simple Tomcat example starts off with a new statement. Same with org.apache.commons.dbcp.BasicDataSourceFactory. And it's the only way I could SessionFactoryObjectFactory get to work. 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
