At least, I was getting a jsessionid; in the urls in testing out the sample I put in the eventcache block.
Is that correct behavior? In that case, I was doing very stateless flow, and didn't really want sessions created.
Geoff
[EMAIL PROTECTED] wrote:
reinhard 2003/07/14 02:54:13
Modified: src/java/org/apache/cocoon/components/flow/javascript/fom
FOM_JavaScriptInterpreter.java
Log:
- changed the comment because implementation has changed
Revision Changes Path
1.2 +5 -4 cocoon-2.1/src/java/org/apache/cocoon/components/flow/javascript/fom/FOM_JavaScriptInterpreter.java
Index: FOM_JavaScriptInterpreter.java
===================================================================
RCS file: /home/cvs/cocoon-2.1/src/java/org/apache/cocoon/components/flow/javascript/fom/FOM_JavaScriptInterpreter.java,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- FOM_JavaScriptInterpreter.java 8 Jul 2003 05:48:52 -0000 1.1
+++ FOM_JavaScriptInterpreter.java 14 Jul 2003 09:54:13 -0000 1.2
@@ -337,8 +337,9 @@
*
* <p>If you want to maintain the state of global variables across
* multiple invocations of <code><map:call
- * function="..."></code>, you need to invoke from the JavaScript
- * script <code>cocoon.createSession()</code>. This will place the
+ * function="..."></code>, you need to instanciate the session
+ * object which is a property of the cocoon object + * <code>var session = cocoon.session</code>. This will place the
* newly create Scriptable object in the user's session, where it
* will be retrieved from at the next invocation of [EMAIL PROTECTED] #callFunction}.</p>
*
