[
http://jira.jboss.com/jira/browse/JBSEAM-2751?page=comments#action_12403736 ]
Norman Richards commented on JBSEAM-2751:
-----------------------------------------
The workaround is to make sure you @In a Datamodel that you @Out from a conversational
component. This will cause Seam to not manage the DataModel specially.
I'm not sure what the correct thing to do here. To do any more would completely break
the current behavior with respect to DataModel fields, however I'm really not sure we
are doing the right thing. I can't see any case where the DataModel wouldn't be
exposed outwardly, either with @Out or with a getter. And when it is, pulling the
DataModel contents out like we do will cause the datamodel to be unusable.
Outjected DataModel looses/forgets wrapped data
-----------------------------------------------
Key: JBSEAM-2751
URL:
http://jira.jboss.com/jira/browse/JBSEAM-2751
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.0.1.GA
Environment: Linux Sarge, JBoss 4.2.2 GA,
Reporter: toni
Assigned To: Norman Richards
Priority: Minor
Fix For: 2.0.2.GA, 2.1.0.GA
Directly outjecting a DataModel into a conversation makes it forget/loose the data
wrapped inside of it.
--
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