[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [equinox-dev] Standardize Eclipse Lazy Start
- From: "Walter Harley" <wharley@xxxxxxx>
- Date: Wed, 8 Nov 2006 18:07:23 -0800
- Delivered-to: firstname.lastname@example.org
- Thread-index: AccCvwXj5nIWZRbPRXup9oX5+OqhIgA5D6gA
- Thread-topic: [equinox-dev] Standardize Eclipse Lazy Start
Tom, I understand this changes the relationship between
bundle activation and class *loading*. What's the relationship between
bundle activation and class *construction*? That is, suppose code in
bundle b calls "new Foo()", where Foo is a class in bundle a.
Does Foo's constructor run before or after a's startup
The Equinox team has been working with the OSGi
Alliance to standardize the Eclipse Lazy Start mechanism (i.e.
Eclipse-LazyStart). See the Equinox WIKI at
http://wiki.eclipse.org/index.php/Lazy_Start_Bundles for details on what is
changing in Eclipse 3.3 with respect to Eclipse-LazyStart.
The initial code changes have been
released to org.eclipse.osgi and will be included in tonight's N-Build.
Please let the Equinox team know if you encounter any unexpected
behavior related to lazy bundle activation.
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated
entities, that may be confidential, proprietary, copyrighted and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.