You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@shale.apache.org by ma...@apache.org on 2007/02/24 13:14:13 UTC
svn commit: r511263 -
/shale/framework/trunk/shale-dialog/src/site/xdoc/index.xml
Author: matzew
Date: Sat Feb 24 04:14:13 2007
New Revision: 511263
URL: http://svn.apache.org/viewvc?view=rev&rev=511263
Log:
DialogContextManager, instead of ...Factory
Modified:
shale/framework/trunk/shale-dialog/src/site/xdoc/index.xml
Modified: shale/framework/trunk/shale-dialog/src/site/xdoc/index.xml
URL: http://svn.apache.org/viewvc/shale/framework/trunk/shale-dialog/src/site/xdoc/index.xml?view=diff&rev=511263&r1=511262&r2=511263
==============================================================================
--- shale/framework/trunk/shale-dialog/src/site/xdoc/index.xml (original)
+++ shale/framework/trunk/shale-dialog/src/site/xdoc/index.xml Sat Feb 24 04:14:13 2007
@@ -130,7 +130,7 @@
with the user. There will be one such instance for each
window or frame running a dialog, stored in session scope.</li>
<li><a href="apidocs/org/apache/shale/dialog/DialogContextManager.html">
- DialogContextFactory</a> - Factory for creating new
+ DialogContextManager</a> - Factory for creating new
<code>DialogContext</code> instances. The Shale Dialog implementation
that you select will provide a suitable factory as a session scope
managed bean under a well-known key. At most one active
@@ -333,7 +333,7 @@
<li>When a POST request for this window is processed, the active
<code>DialogContext</code> instance for the logical dialog
identifier for this window will be retrieved from the
- <code>DialogContextFactory</code> for this user, and stored
+ <code>DialogContextManager</code> for this user, and stored
as a request scope attribute under key <code>dialog</code>
for easy reference in expressions.</li>
<li>During <em>Invoke Application</em> phase of the request