Mailing-List: contact docs-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: docs@cocoon.apache.org
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
From: docs@cocoon.apache.org
To: docs@cocoon.apache.org
Subject: 
 =?iso-8859-1?q?=5BCocoon_Wiki=5D_Updated=3A__FlowscriptAndSessionReplicat?=
 =?iso-8859-1?q?ion?=
Date: Fri, 14 Jan 2005 08:27:36 -0000
Message-ID: <20050114082736.81634.76562@minotaur.apache.org>

   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 b=
e serialized (the session itself, the source resolver, etc) the above strat=
egy would at least need to applied to them.  In addition, objects created b=
y the user that are referenced via the Rhino global scope or the local vari=
ables 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
+
 =3D=3D Plugging in the solution into existing containers =3D=3D
 =3D=3D=3D Description =3D=3D=3D
 The serialization/deserialization process of Java objects has to be overri=
den (see explanations by Chris). This mechanism has to be plugged into the =
container without having to modify it.