[
https://jira.jboss.org/jira/browse/JBSEAM-3493?page=com.atlassian.jira.pl...
]
Francisco Jose Peredo Noguez commented on JBSEAM-3493:
------------------------------------------------------
I am starting to suspect that the class doing this magic encapsulation violation for
non-transient member fields is org.jboss.seam.persistence.ManagedEntityIdentityInterceptor
with help of the advanced black magic of org.jboss.seam.util.Reflections. Sadly,
Reflections has no logging support so I am going to have to add it to see if is the source
of this strange behavior.
The EntityHome should not preserve the value of its instance property
after entering a nested conversation when having the @PerNestedConversation annotation
------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBSEAM-3493
URL:
https://jira.jboss.org/jira/browse/JBSEAM-3493
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.0.2.SP1
Reporter: Francisco Jose Peredo Noguez
Attachments: SeamRecursionTestCase.zip
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.
--
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