svn commit: r629771 - /myfaces/orchestra/trunk/maven/src/site/xdoc/index.xml

[sk...@apache.org]

Author: skitching
Date: Thu Feb 21 05:13:58 2008
New Revision: 629771

URL: http://svn.apache.org/viewvc?rev=629771&view=rev
Log:
Point out that Orchestra persistence is a web-tier-only solution.

Modified:
    myfaces/orchestra/trunk/maven/src/site/xdoc/index.xml

Modified: myfaces/orchestra/trunk/maven/src/site/xdoc/index.xml
URL: http://svn.apache.org/viewvc/myfaces/orchestra/trunk/maven/src/site/xdoc/index.xml?rev=629771&r1=629770&r2=629771&view=diff
==============================================================================
--- myfaces/orchestra/trunk/maven/src/site/xdoc/index.xml (original)
+++ myfaces/orchestra/trunk/maven/src/site/xdoc/index.xml Thu Feb 21 05:13:58 2008
@@ -89,6 +89,17 @@
 				</ul>
 			</subsection>
 
+			<subsection name="Limitations">
+			<p>
+			Orchestra persistence features presume the presentation tier has access to the database,
+			i.e. that the presentation and database-access tiers are combined. This is often the case
+			in small-to-medium web applications. Large or security-sensitive applications which separate
+			database access out into an isolated tier (eg use a "full EB stack") cannot use the Orchestra
+			persistence facilities, although they can still make use of the regular conversational support
+			for beans in the presentation layer.
+			</p>
+			</subsection>
+
 			<subsection name="A small JSF example">
 				<p>For the impatient, here's a quick demonstration of Orchestra's main features.</p>