[ http://jira.jboss.com/jira/browse/JBSEAM-1487?page=all ] Pete Muir updated JBSEAM-1487: ------------------------------ Fix Version/s: (was: 1.3.0.GA) Description: The refactoring of the entity converter requires entities to be managed. If they are not the following exception is thrown: org.hibernate.TransientObjectException: The instance was not associated with this session. For me this is an api regression and therefore a blocker because it may introduce very nasty bugs which will be hard to detect. While a work around exists (see below) it is not easy to refactor existing application accordingly. Therefore this may effectively prevent many people from upgrading to JBoss 4.2.0/Seam 1.3.0. (This is just my personal opinion and sort - feel free to downgrade this bug!) Would it be possible to catch the exception and fall back to the old behavior? was: The refactoring of the entity converter requires entities to be managed. If they are not the following exception is thrown: org.hibernate.TransientObjectException: The instance was not associated with this session. For me this is an api regression and therefore a blocker because it may introduce very nasty bugs which will be hard to detect. While a work around exists (see below) it is not easy to refactor existing application accordingly. Therefore this may effectivly prevent many people from upgrading to JBoss 4.2.0/Seam 1.3.0. (This is just my personal opinion and sort - feel free to downgrade this bug!) Would it be possible to catch the exception and fall back to the old behaviour? Assignee: Pete Muir -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-1487?page=all ] Pete Muir updated JBSEAM-1487: ------------------------------ Fix Version/s: (was: 2.0.0.CR1) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-1487?page=all ] Pete Muir updated JBSEAM-1487: ------------------------------ Attachment: JBSEAM-1487.patch This patch to HEAD should fix it - please test it for me :) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-1487?page=all ] Pete Muir resolved JBSEAM-1487. ------------------------------- Resolution: Done -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira