Hmmm. I think we're refering to two different things. What I mean by the
extender pattern is where a bundle (the extender bundle) *extends* other
bundles in some domain-specific way based on some criteria, typically
the contents of the bundle or the manifest (or both).
Typically, I've seen this implemented with a two-phase approach upon
activation of the extender bundle:
1) Extend any existing bundles
2) Watch for new bundles
It sounds from what you are saying that EclipseLink and DOSGi only do
#2, not #1.
See http://www.aqute.biz/Snippets/Extender for more information.
Justin
On 1/29/10 2:17 PM, Joel Schuster wrote:
No extender pattern in these cases, dependency is not by extension, just by
indirect usage.
- Joel
-----Original Message-----
From: Justin Edelson [mailto:[email protected]]
Sent: Friday, January 29, 2010 11:45 AM
To: [email protected]
Subject: Re: FileInstall at different start levels
These seem like bugs in Eclipselink and your DOSGi implementation. The
extender pattern should apply to bundles started before AND after the
extender bundle.
Justin
On Jan 29, 2010, at 1:12 PM, Joel Schuster<[email protected]> wrote:
Just to clarify. The reason I run into problems is that there are no
direct dependencies between some bundles.
Example:
DB bundle that has a persistence.xml needs to be loaded AFTER
Eclipselink bundle that resisters for notification of DB bundles
being loaded so that it can go and look for the xml file. If
Eclipselink is loaded after DB bundle then the persistence context
is not available to some other bundle that uses Eclipselink and DB
bundle directly.
This is also true for DOSGI, it has to be loaded before any bundles
that might have declarations to expose a service as a web service.
If the bundle that's trying to be exposed gets loaded first then
DOSGI will miss it's opportunity.
- Joel
-----Original Message-----
From: Joel Schuster [mailto:[email protected]]
Sent: Friday, January 29, 2010 11:00 AM
To: [email protected]
Subject: FileInstall at different start levels
Is there any way to have multiple different FileInstall instances
have different start levels?
I'm using FileInstall with multiple cfgs (up to 10), each monitoring
different bundle/config directories depending on how I need to
configure my run time.
I'm running into cases where one set needs to be all started before
another set of bundles come up.
Any suggestions?
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
