You are viewing a plain text version of this content. The canonical link for it is here.

Posted to docs@cocoon.apache.org by do...@cocoon.apache.org on 2005/01/14 09:27:36 UTC

[Cocoon Wiki] Updated: FlowscriptAndSessionReplication

   Date: 2005-01-14T00:27:36
   Editor: ReinhardPoetz
   Wiki: Cocoon Wiki
   Page: FlowscriptAndSessionReplication
   URL: http://wiki.apache.org/cocoon/FlowscriptAndSessionReplication

   some references to Javadocs

Change Log:

------------------------------------------------------------------------------
@@ -63,6 +63,14 @@
 
 Since the FOM objects refer to underlying Cocoon objects that should not be serialized (the session itself, the source resolver, etc) the above strategy would at least need to applied to them.  In addition, objects created by the user that are referenced via the Rhino global scope or the local variables of a continuation may need this treatment. 
 
+---
+See also
+
+ * http://java.sun.com/j2se/1.4.2/docs/guide/serialization/spec/output.html
+ * http://java.sun.com/j2se/1.4.2/docs/api/java/io/ObjectOutputStream.html
+ * http://java.sun.com/j2se/1.4.2/docs/api/java/io/ObjectInputStream.html
+ * http://java.sun.com/j2se/1.4.2/docs/api/java/io/Serializable.html
+
 == Plugging in the solution into existing containers ==
 === Description ===
 The serialization/deserialization process of Java objects has to be overriden (see explanations by Chris). This mechanism has to be plugged into the container without having to modify it.