|
»
« Return to Thread: Continuation sadness
Re: Continuation sadness
Hi Patrick,
that is possible in the RIFE version of continuations. While
stripping it out you seem to have removed the feature. Line 140 of
ContinuationManager reads "if (true)", while in the RIFE version this
checks for a setting that indicates if the cloning should happen or not.
One thing that also really helps to work around these errors, is to
simply extract the piece of logic that contains unclonable variables
into a dedicated method. It will then not be instrumented.
Hope this helps,
Geert
On 16-feb-06, at 03:03, Patrick Lightbody wrote:
> Getting these errors in my WebWork action when using continuations:
>
> com.uwyn.rife.continuations.exceptions.LocalVariableUncloneableExcepti
> on: The implementation
> 'com.autoriginate.litmus.action.IntroduceMacroAction' uses a local
> method variable of type 'java.util.AbstractList$Itr' which is not
> cloneable.
>
> I believe it is coming from this particular line:
>
> for (long id : commandIds) {
>
> Though I can't be sure.
>
> Is there any way to deal with uncloneable variables? Perhaps we can
> introduce an interface that indicates that the continuation support
> shouldn't "remember" multiple states, allowing RIFE/Continuations
> to simply use the original variable rather than clone it?
>
> Patrick
>
> _______________________________________________
> Rife-devel mailing list
> Rife-devel@...
> http://lists.uwyn.com/mailman/listinfo/rife-devel
>
--
Geert Bevin Uwyn bvba
"Use what you need" Avenue de Scailmont 34
http://www.uwyn.com 7170 Manage, Belgium
gbevin[remove] at uwyn dot com Tel +32 64 84 80 03
PGP Fingerprint : 4E21 6399 CD9E A384 6619 719A C8F4 D40D 309F D6A9
Public PGP key : available at servers pgp.mit.edu, wwwkeys.pgp.net
_______________________________________________
Rife-devel mailing list
Rife-devel@...
http://lists.uwyn.com/mailman/listinfo/rife-devel
that is possible in the RIFE version of continuations. While
stripping it out you seem to have removed the feature. Line 140 of
ContinuationManager reads "if (true)", while in the RIFE version this
checks for a setting that indicates if the cloning should happen or not.
One thing that also really helps to work around these errors, is to
simply extract the piece of logic that contains unclonable variables
into a dedicated method. It will then not be instrumented.
Hope this helps,
Geert
On 16-feb-06, at 03:03, Patrick Lightbody wrote:
> Getting these errors in my WebWork action when using continuations:
>
> com.uwyn.rife.continuations.exceptions.LocalVariableUncloneableExcepti
> on: The implementation
> 'com.autoriginate.litmus.action.IntroduceMacroAction' uses a local
> method variable of type 'java.util.AbstractList$Itr' which is not
> cloneable.
>
> I believe it is coming from this particular line:
>
> for (long id : commandIds) {
>
> Though I can't be sure.
>
> Is there any way to deal with uncloneable variables? Perhaps we can
> introduce an interface that indicates that the continuation support
> shouldn't "remember" multiple states, allowing RIFE/Continuations
> to simply use the original variable rather than clone it?
>
> Patrick
>
> _______________________________________________
> Rife-devel mailing list
> Rife-devel@...
> http://lists.uwyn.com/mailman/listinfo/rife-devel
>
--
Geert Bevin Uwyn bvba
"Use what you need" Avenue de Scailmont 34
http://www.uwyn.com 7170 Manage, Belgium
gbevin[remove] at uwyn dot com Tel +32 64 84 80 03
PGP Fingerprint : 4E21 6399 CD9E A384 6619 719A C8F4 D40D 309F D6A9
Public PGP key : available at servers pgp.mit.edu, wwwkeys.pgp.net
_______________________________________________
Rife-devel mailing list
Rife-devel@...
http://lists.uwyn.com/mailman/listinfo/rife-devel
« Return to Thread: Continuation sadness
| Free embeddable forum powered by Nabble | Forum Help |
