-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
stop() method is never called in cached controllers #142
Comments
Some assumptions: ComponentController removeFromCache(this) clearControllerCache()
DO NOT CALL THIS METHOD INSIDE A CACHED CONTROLLER! ComponentCompositeController removeFromCache(this) clearControllerCache() |
Please, switch the Nalu version to HEAD-SNAPSHOT and try again. Just deployed a new SNAPSHOT version containing the fix. Keep in mind, that the Debug annotation is no longer supported. Just delete the code, if you have used it. |
Fixed |
Please add possibility to stop() cached controllers.
We have method:
router.clearCache();
Whenever We wanna clear caches it is a good place to call stop() method on each cached controllers- f.e.: when You logs out from app.
Second option would be add method f.e.:
<C extends AbstractComponentController<?, ?, ?>> void removeFromCacheAllControllers();
so when User logs out he can trigger cache clean up.
I think whenever cached controller is removed from cache it should execute its stop() method, cause start method (start caching controller) is executed, but stop method is never executed.
start()/stop() methods starts controllers and its tasks( timers/ handlers etc)
activate()/deactivate() methods are triggered when controller/view is routed to and out and some task may run in background.
We need to have stop() be triggered.
The text was updated successfully, but these errors were encountered: