Date: 2005-01-14T01:20:50 Editor: ReinhardPoetz Wiki: Cocoon Wiki Page: FlowscriptAndSessionReplication URL: http://wiki.apache.org/cocoon/FlowscriptAndSessionReplication
another problem; additional link Change Log: ------------------------------------------------------------------------------ @@ -70,6 +70,7 @@ * 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 + * http://wiki.apache.org/cocoon/RhinoWithContinuations == Plugging in the solution into existing containers == === Description === @@ -85,3 +86,18 @@ === Possible solution === Add some kind of delta management into the serialization/deserialization process. But how ...? + +== Components managed by the Cocoon service manager == +== Description == +If components are used in flow that are managed by the Cocoon service manager, we have to make sure that the references in the target JVM are still valid. + +{{{ +function xy() { + var x = cocoon.getComponent("myComponent"); + var y = cocoon.createObject("myObjectImplementingAvalonInterfaces"); +} +}}} + +== Possible solution == + * Forbid the usage of components + * ''... how to manage references to service manager or service selector? May be through serializable proxies... Or may be by documenting that no flow method should have non-serializable objects on stack...'' by Vadim
