[ http://opensource.atlassian.com/projects/hibernate/browse/HHH-1258?page=c... ] Tyler Van Gorder commented on HHH-1258: --------------------------------------- Hi Max, I got some time at a recent conference to work on a 3.2 version of the "on-demand" configuration loading. A couple of comments: - This patch is intended to ONLY be used in a testing environment - This patch is strictly to the SessionFactoryImpl - This patch is not yet thread-safe. What I have done: - The sessionfactory implementation keeps a reference to both the configuration and mapping objects. - There is a boolean "onDemandConfiguration" to turn this "patch" on/off. - The maps : entityPersisters, classMetadata, collectionPersisters, collectionMetadata have been made mutable. - Initialization (when the patch is on) still populates the maps however, the maps contain PersistentClass (for entityPersisters) and Collection (for collectionPersisters) - Any place where either the entityPersisters or collectionPersisters map is accessed, I check the type, if its a PersistentClass then I create the entityPersister at that point and replace the entry in the map. ditto for Collection. My only concern is the following method: "getImplementors" - I am not sure I am doing everything correct in here when the entry is a PersistentClass rather than an EntityPersister. Finally, thread safety: This should be totally doable, I don't think I can add a monitor to each map, because they may be accessed in different orders and result in a deadlock, which means there needs to be one monitor for all the mutable maps. What are your thoughts on this? Thanks. Tyler. See attatched file: -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.... - For more information on JIRA, see: http://www.atlassian.com/software/jira