[ http://opensource.atlassian.com/projects/hibernate/browse/EJB-274?page=co... ] Reto Ferri commented on EJB-274: -------------------------------- My idea behind this question is to inject an EntityManager (and nothing more) to all loaded or persisted entities(with the @PersistenceContext attribute). This seems for me a natural and good way to obtain an EntityManager also in an standanlone application. You still need to create an initial EntityManager and to set the transaction boundaries there, but from then you could rely on the injection of the EntityManager as in a container environment. As far as I can see, this would also allow to write entity beans which are usefull in standalone and container applications and it would avoid coupling of entity beans to a globally visible EntityManager. -- 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-274?page=co... ] Reto Ferri commented on EJB-274: -------------------------------- All objects loaded throught the entity manager are not the problem, because then the em is resposible for loading and creating the new object and can inject itself easily. All newly created and persisted objects have to be added to the entity manager through the call of persist (as far as I have understood the specs), or at least a developer of a bean library could code it that way to achieve more flexibility. -- 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-274?page=co... ] Reto Ferri commented on EJB-274: -------------------------------- As far as I know, garbage collector like removing is not supported by the specs. Therefore in a container - contained relationship I have to explicitly call em.remove(contained) besides the normal removing from both sides of a relationship. This could be nicely done with an injected em. -- 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-274?page=co... ] Reto Ferri commented on EJB-274: -------------------------------- Well, Im am writing complex OO applications for 20 years and I am using Hibernate for 1 year, and thank you for your kind advise :) There are certainly occasions where cascading cannot or should not be used. Even in your own book you'r mentioning that cascading not always is the best way. But obiously there are other ways of doing it which are not covered in your book. Your right, I read the specs again and they don't require to inject em into entity beans. To sum this discussion up : - no plans to implement em injection - the idea itself is considered senseless One final question : Do you want me to publish my code changes here? -- 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