commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefano Bagnara (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SANDBOX-213) [javaflow] In class 'Stack' a non serializable object (Runnable) is written to ObjectOutput
Date Sat, 13 Sep 2008 14:52:44 GMT

    [ https://issues.apache.org/jira/browse/SANDBOX-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630777#action_12630777
] 

Stefano Bagnara commented on SANDBOX-213:
-----------------------------------------

I think this is an expected behaviour. In order to use the persistence for continuations you
have to make sure that everything your want to suspend/continue is serializable.
If not you can still use Continuations but you can't use the persistence for the stack.

If I misunderstood your issue can you provide a test case for it?


> [javaflow] In class 'Stack' a non serializable object (Runnable) is written to ObjectOutput
> -------------------------------------------------------------------------------------------
>
>                 Key: SANDBOX-213
>                 URL: https://issues.apache.org/jira/browse/SANDBOX-213
>             Project: Commons Sandbox
>          Issue Type: Bug
>          Components: Javaflow
>            Reporter: Philip May
>
> The class Stack writes a non serializable object (Runnable) to ObjectOutput:
> protected Runnable runnable;
> s.writeObject(runnable);
> This code seems to be passing a non-serializable object to the ObjectOutput.writeObject
method. If the object is, indeed, non-serializable, an error will result. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message