[ https://jira.jboss.org/jira/browse/JBSEAM-3493?page=com.atlassian.jira.pl... ] Francisco Jose Peredo Noguez commented on JBSEAM-3493: ------------------------------------------------------ the problem described here gets fixed by adding in org.jboss.seam.framework.Home the transient keyword to the instance variable (it works,but I do not understad why): protected transient E instance; -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3493?page=com.atlassian.jira.pl... ] Pete Muir commented on JBSEAM-3493: ----------------------------------- Please attach a simple example to allow us to reproduce. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3493?page=com.atlassian.jira.pl... ] Francisco Jose Peredo Noguez updated JBSEAM-3493: ------------------------------------------------- Attachment: SeamRecursionTestCase.zip In CategoryHome.java just uncomment the line with the transient keyword, and the bug will dissapear: //private transient Category backupInstance; private Category backupInstance; @Override public Category getInstance() { // TODO Auto-generated method stub this.setInstance(backupInstance); return super.getInstance(); } @Override public void setInstance(Category instance) { // TODO Auto-generated method stub super.setInstance(instance); backupInstance=instance; } -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3493?page=com.atlassian.jira.pl... ] Francisco Jose Peredo Noguez updated JBSEAM-3493: ------------------------------------------------- Affects Version/s: 2.1.0.SP1 Description: I have a reflective 1-n associations e.g. Person child of Person. I would like to create a child from the PersonEdit.xhtml created by seam-gen then adapted by hand. When I put @PerNestedConversation annotation to my PersonHome the behavior seems to be ok. Each conversation has it's own instance of PersonHome. BUT all of those instances is wired to the same instance of Person (the Entity)... I've tried to trace modifications on the "instance" field of Home but it's never set; it should stay to null and then call createInstance() but this never happen because the Person instance is the same as the parent conversation one. Update: If I ManagedEntityInterceptor is disabled (default configuration in Seam 2.1.0SP1) this problem disappears (and of course it returns if I re-enable it in components.xml). This means ManagedEntityInterceptor and PerNestedConversation are incompatible. was: I have a reflective 1-n associations e.g. Person childof Person. I would like to create a child from the PersonEdit.xhtml created by seam-gen then adapted by hand. When I put @PerNestedConversation annotation to my PersonHome the behavior seems to be ok. Each conversation has it's own instance of PersonHome. BUT all of those instances is wired to the same instance of Person (the Entity)... I've tried to trace modifications on the "instance" field of Home but it's never set; it should stay to null and then call createInstance() but this never happen because the Person instance is the same as the parent conversation one. Description updated for 2.1.0SP1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3493?page=com.atlassian.jira.pl... ] Francisco Jose Peredo Noguez updated JBSEAM-3493: ------------------------------------------------- Summary: Incompatibilty between PerNestedConversation and ManagedEntityInterceptor detected when trying to create a CRUD for a reflective 1-n associations (was: The EntityHome should not preserve the value of its instance property after entering a nested conversation when having the @PerNestedConversation annotation) Description: I have a reflective 1-n associations e.g. Person child of Person. I would like to create a child from the PersonEdit.xhtml created by seam-gen then adapted by hand. When I put @PerNestedConversation annotation to my PersonHome the behavior seems to be ok. Each conversation has it's own instance of PersonHome. BUT all of those instances is wired to the same instance of Person (the Entity)... I've tried to trace modifications on the "instance" field of Home but it's never set; it should stay to null and then call createInstance() but this never happen because the Person instance is the same as the parent conversation one. Update for Seam 2.1.0SP1: If I ManagedEntityInterceptor is disabled (default configuration now) this problem disappears (and of course it returns if I re-enable it in components.xml). This means that the root cause of this problem is that ManagedEntityInterceptor and PerNestedConversation are incompatible. was: I have a reflective 1-n associations e.g. Person child of Person. I would like to create a child from the PersonEdit.xhtml created by seam-gen then adapted by hand. When I put @PerNestedConversation annotation to my PersonHome the behavior seems to be ok. Each conversation has it's own instance of PersonHome. BUT all of those instances is wired to the same instance of Person (the Entity)... I've tried to trace modifications on the "instance" field of Home but it's never set; it should stay to null and then call createInstance() but this never happen because the Person instance is the same as the parent conversation one. Update: If I ManagedEntityInterceptor is disabled (default configuration in Seam 2.1.0SP1) this problem disappears (and of course it returns if I re-enable it in components.xml). This means ManagedEntityInterceptor and PerNestedConversation are incompatible. Renamed issue due to recent findings -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-3493?page=com.atlassian.jira.pl... ] Francisco Jose Peredo Noguez commented on JBSEAM-3493: ------------------------------------------------------ Salim... I would recommend you to download SeamRecursionTestCase.zip and see if you solution really works... also make sure that ManagedEntityInterceptor is enabled, because in Seam latest versions, is disabled by default -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira