svn commit: r980531 - in /websites/production/tapestry/content: cache/main.pageCache google-app-engine.html

[bu...@apache.org]

Author: buildbot
Date: Tue Feb 16 02:20:02 2016
New Revision: 980531

Log:
Production update by buildbot for tapestry

Modified:
    websites/production/tapestry/content/cache/main.pageCache
    websites/production/tapestry/content/google-app-engine.html

Modified: websites/production/tapestry/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/tapestry/content/google-app-engine.html
==============================================================================
--- websites/production/tapestry/content/google-app-engine.html (original)
+++ websites/production/tapestry/content/google-app-engine.html Tue Feb 16 02:20:02 2016
@@ -78,7 +78,7 @@
              configuration.add(IOCSymbols.THREAD_POOL_ENABLED, "false");
              ...
 &#160;&#160;&#160;&#160; }</pre>
-</div></div><p>NOTE: Setting production mode to true is generally only desirable in production and QA/testing environments), but you can override that symbol with a JVM system property (<code>-Dtapestry.production-mode=false</code>) in those environments.</p><h2 id="GoogleAppEngine-SerializableObjects">Serializable Objects</h2><ul><li>Make sure all objects that you store in the servlet session -- particularly those annotated with @SessionState and&#160;@SessionAttribute&#160;&#8211; are actually serializable types. Otherwise you may see strange behavior in which objects seem to lose their session values.</li></ul><h2 id="GoogleAppEngine-OtherConsiderations">Other Considerations</h2><p>Other than the above settings, Tapestry should provide no impediment to running your app under Google App Engine. However, you still need to adhere to all of GAE's usual constraints (as with any app, Tapestry or otherwise). Please carefully read Google's documentation for general guidelines for creatin
 g an app that is compatible with GAE.</p></div>
+</div></div><p>NOTE: Setting production mode to true is generally only desirable in production and QA/testing environments, but you can override that symbol with a JVM system property (<code>-Dtapestry.production-mode=false</code>) in those environments.</p><h2 id="GoogleAppEngine-SerializableObjects">Serializable Objects</h2><ul><li>Make sure all objects that you store in the servlet session -- particularly those annotated with @SessionState and&#160;@SessionAttribute&#160;&#8211; are actually serializable types. Otherwise you may see strange behavior in which objects seem to lose their session values.</li></ul><h2 id="GoogleAppEngine-FileUploads">File Uploads</h2><ul><li>If you use the Tapestry-upload module (or any file upload mechanism, for that matter), you'll need to be sure that it is configured to <em>not</em> store temporary uploaded files on the file system.&#160; See <a  href="uploading-files.html">Uploading Files</a>&#160;&#8211; particularly the <code>upload.repository-
 threshold</code> symbol, which should be set to a large value.</li></ul><h2 id="GoogleAppEngine-OtherConsiderations">Other Considerations</h2><p>Other than the above settings, Tapestry should provide no impediment to running your app under Google App Engine. However, you still need to adhere to all of GAE's usual constraints (as with any app, Tapestry or otherwise). Please carefully read Google's documentation for general guidelines for creating an app that is compatible with GAE.</p></div>
       </div>
 
       <div class="clearer"></div>