[
https://jira.jboss.org/jira/browse/JBSEAM-3493?page=com.atlassian.jira.pl...
]
Pete Muir updated JBSEAM-3493:
------------------------------
Summary: The EntityHome should not preserve the value of its instance property
after entering a nested conversation when having the @PerNestedConversation annotation
(was: The EntityHome should not preserve the value of its instance property after entering
a nested transaction when having the @PerNestedConversation annotation)
Description:
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.
was:
I have a reflective 1-n associations like
Person childof Person.
I would like to create a child from the PersonEdit.xhtml created by seam-gen then adapted
by hands...
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 setted so it should stay to null and then call my createInstance()
overrided method....but this never happen because (as I said) Person instance is the same
as the parent conversation one....
Did I miss something?
Or is this a limitation of the CRUD framework?
nowhere on the code the field "instance" is setted so I believe this is due to
javassist proxying that my eclipse debugger can't see...
If this feature isn't working how would you implement my "Create child"
button to create a new Person has a child of the current conversation
"personHome.instance" ?...
Please try to make your bug reports intelligible by not including speculation, rhetorical
questions, questions about workarounds. I edited the summary to give you an idea.
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
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