You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because of components are cleanup in a random order, component not found exceptions appears. Ignore theres errors during a cleanUp.
Code proposition for ComponentManager class :
cleanUp
<script: 'self cleanUp'>
| notifiers subscribers |
"CleanUp and initialize the ComponentFactory"
MolComponentFactory cleanUp.
MolComponentFactory initialize.
Default ifNil:[^self].
Default locatorServices eventsSubscribers: nil.
notifiers := MolEventNotifier allInstances.
subscribers := MolEventSubscriber allInstances.
"Ignore some Error during the cleanUp because the clean process can be different of the start order"
[Default release] on: ComponentAlreadyPassivatedError, ComponentNotFoundError do:[ :e | "do nothing" ].
Default := nil.
notifiers do: [:n | n release].
subscribers do: [:n | n release].
The text was updated successfully, but these errors were encountered:
labordep
changed the title
Bug : Cannot cleanUp with a started Component Tree
Bug : AlreadyPassivate and ComponentNotFound errors are raised during a ComponentManager>>cleanUp
Dec 23, 2020
Because of components are cleanup in a random order, component not found exceptions appears. Ignore theres errors during a cleanUp.
Code proposition for ComponentManager class :
The text was updated successfully, but these errors were encountered: