Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

E4/EAS/Life Cycle

< E4‎ | EAS
Revision as of 12:48, 22 October 2009 by Boris Bokowski.ca.ibm.com (Talk | contribs)

Components (UI or non-UI) very often manage resources that need to be initialized when the component is instantiated, or disposed when the component itself is disposed. This is a long-winded way of saying that a container should call a method after a component is instantiated and ready to go, and call another method just before disposing the component.

Java

Use JSR-250 annotations @PostConstruct and @PreDestroy to mark methods that should be called by the framework.

Alternatively, if a component implements IDisposable, the framework should call IDisposable.dispose().

JavaScript

Initialization is often handled by registering an "on load" handler from the script that is evaluated as part of instantiating the component. Not sure if "on unload" is widely used. It would make sense to list functions to call on load and unload in the component metadata.

Back to the top