[ http://opensource.atlassian.com/projects/hibernate/browse/EJB-402?page=co... ] Emmanuel Bernard commented on EJB-402: -------------------------------------- galder The problem is that Ejb3ConfigurationObjectFactory currently uses ObjectInputStream to read the Ejb3Configuration from JNDI. If the deployment is isolated, reading this configuration fails because it tries to resolve classes that are isolated. I don't know, you created Ejb3ConfigurationObjectFactory in the 1st place so you should know why you did that: 9/6/06 "EJB-160 make Ejb3Configuration and AnnotationConfiguration serializable and allow JNDI reference" I don't know SessionFactoryObjectFactory enough to be able to say whether the configuration could be retrieved in the same way or not but SessionFactoryObjectFactory looks more recent and does not require the use of an OIS or MVIS so that's probably a better way of getting the required configuration object from JNDI rather than introducing a dependency on AS. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/EJB-402?page=co... ] Emmanuel Bernard commented on EJB-402: -------------------------------------- I did copy SessionFactoryObjectFactory when I wrote he ejb3ConfigurationObjectFactory. But I can't use the naming trick because a configuration does not have a defined lifecycle. I am not sure if we can achieve serializability and portability still. WDYT? -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/EJB-402?page=co... ] Emmanuel Bernard commented on EJB-402: -------------------------------------- Galder Hi Emmanuel, Apologies for not replying earlier but I've been on holiday and I'm not catching on old mails. I dunno much about Hibernate but could you explain what is the role of these Configuration objects and why do you say that they're not tied to a defined lifecycle? They're the configuration of what? EntityManager? EntityManagerFactory? Cheers, -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/EJB-402?page=co... ] Emmanuel Bernard commented on EJB-402: -------------------------------------- This code can't be in JBoss AS as HEM works for any app server. There must be a standard solution to this problem. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/EJB-402?page=co... ] Galder Zamarreno commented on EJB-402: -------------------------------------- Yeah, a CNFE is raised when reading the configuration because the Entities that are reading are deployed in an isolated deployment and when reading the configuration, the right classloader, the one associated with the thread is not set (MarshalledValueInputStream does this), hence it's not found. I'm not sure whether you can easily find a solution that lives in HB and that works for all app servers. I know what works for JBoss AS and that solution imo, should live in the integration/ project in the same way that Arjuna put there the code that integrated Arjuna TM with AS: http://lists.jboss.org/pipermail/jboss-development/2007-July/010319.html One last thing, who and when are these EMF objects build? EM objects are build upon deployment of an archive containing a persistence unit. -- 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

[ http://opensource.atlassian.com/projects/hibernate/browse/EJB-402?page=co... ] Emmanuel Bernard updated EJB-402: --------------------------------- Fix Version/s: (was: 3.4.0.GA) 3.5 -- 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