Thorsten Scherler schrieb:
On Tue, 2008-02-26 at 16:02 -0800, [EMAIL PROTECTED] wrote:
http://issues.apache.org/bugzilla/show_bug.cgi?id=43240
I did some memory profiling with the MultiWorkflow usecase and noticed two
problems:
1. Continuations aren't invalidated and eat up memory.
2. The MultiWorkflow usecase creates a continuation but doesn't need one.
I have added some code to invalidate the continuation to usecases.js and added
the createContinuation="false" attribute to the MultiWorkflow view declaration.
We should be very careful to add this attribute to all view declarations which
don't need a continuation.
Is there a general rule of thumb when a usecase needs continuation and
when not? I guess having this will lower the impact.
A usecase view needs a continuation if the usecase reacts to user
interaction. This is usually the case if it implements advance() and/or
doExecute(). I guess we should add this to the documentation.
-- Andreas
--
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch
Tel.: +41 (0) 43 818 57 01
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
