User: mulder
Date: 00/10/12 11:24:15
Modified: manual examples.html
Log:
Forgot one code change for the pet store - logoff handling.
Revision Changes Path
1.4 +13 -0 jbossweb/manual/examples.html
Index: examples.html
===================================================================
RCS file: /products/cvs/ejboss/jbossweb/manual/examples.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- examples.html 2000/10/12 18:13:20 1.3
+++ examples.html 2000/10/12 18:24:15 1.4
@@ -25,6 +25,7 @@
<li><a HREF="#petstore4">Resolve the Catalog DB Situation</a></li>
<li><a HREF="#petstore5">Resolve the Account Situation</a></li>
<li><a HREF="#petstore6">Resolve the JNDI Situation</a></li>
+ <li><a HREF="#petstore6.5">Resolve the Logoff Situation</a></li>
<li><a HREF="#petstore7">Prepare the Database</a></li>
<li><a HREF="#petstore8">Add DB Pool to jBoss</a></li>
<li><a HREF="#petstore9">Correct the Server Name</a></li>
@@ -151,6 +152,18 @@
throw new GeneralFailureException(e);
}
</pre>
+
+ <h3><a NAME="petstore6.5">Resolve the Logoff Situation</a></h3>
+ <p>When you log off of the pet store, it tries to invalidate
+ the current servlet session and then immediately grab a new
+ one to initialize. This fails in Tomcat, since you can't
+ get a new session until you've loaded a new page. You can
+ solve this by patching Tomcat (not recommended) or changing
+ the file
+ <code>src/com/sun/estore/control/web/RequestProcessor.java</code>
+ around line 121 (where it handles the logoff event) so it
+ just invalidates the current session and does not try to
+ generate a new one.</p>
<h3><a NAME="petstore7">Prepare the Database</a></h3>
<p>The default configuration assumes the Cloudscape database.
