>> Now as for this issue of the MBean needing classpath to the persistent classes, am I right in assuming that no management calls to the MBean would ever be able to see the application classpath? <<
I believe that is the case. My (limited) understanding is that anything in an EJB jar gets its own class path and class loader seperate from the rest of the server and other EJBs. >> If so, is a possible solution to create a new implentation of the SessionFactory interface that creates a datastore and builds a SessionFactory when first invoked by the application ... and then forwards requests to the actual SessionFactory implementation? << Only if everything is in one big EJB jar file. If they are split between seperate EJB jar files, then there is still a problem. If one was to put mappings in seperate files for each class (like the eg/Foo.hbm.xml and eg/Bar.hbm.xml example in the docs), you could wait to load the mapping for a class until the class was first accessed. That might fix the problem. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Hibernate-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/hibernate-devel
