You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@myfaces.apache.org by im...@apache.org on 2007/10/09 10:47:40 UTC
svn commit: r583075 - /myfaces/orchestra/trunk/core/src/site/xdoc/faqs.xml
Author: imario
Date: Tue Oct 9 01:47:39 2007
New Revision: 583075
URL: http://svn.apache.org/viewvc?rev=583075&view=rev
Log:
faq: entity between conv
Modified:
myfaces/orchestra/trunk/core/src/site/xdoc/faqs.xml
Modified: myfaces/orchestra/trunk/core/src/site/xdoc/faqs.xml
URL: http://svn.apache.org/viewvc/myfaces/orchestra/trunk/core/src/site/xdoc/faqs.xml?rev=583075&r1=583074&r2=583075&view=diff
==============================================================================
--- myfaces/orchestra/trunk/core/src/site/xdoc/faqs.xml (original)
+++ myfaces/orchestra/trunk/core/src/site/xdoc/faqs.xml Tue Oct 9 01:47:39 2007
@@ -92,6 +92,17 @@
Orchestra already does this for you.
</p>
</subsection>
+
+ <subsection name="Is it possible to pass an entity from one conversation scoped bean to another?">
+ <p><br>No!</br></p>
+ <p>
+ The reason is, that the entity is associated with a persistent context which is
+ different between the various conversation scoped beans.<br />
+ You are safe if you just pass the surrogating key around.<br />
+ This is not an Orchestra limitation, but more a technical limitation of how
+ the ORM work today.
+ </p>
+ </subsection>
</section>
</body>
</document>