felix-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard S. Hall" <he...@ungoverned.org>
Subject Re: Programatically create package dependencies for a bundle
Date Wed, 18 Jan 2012 16:04:58 GMT
On 1/18/12 10:29 , Daniel Spicar wrote:
> On 18 January 2012 16:11, Richard S. Hall<heavy@ungoverned.org>  wrote:
>
>> I agree it isn't the best, since all service clients would need to add the
>> dynamic import. Perhaps you need to think about restructuring your service.
>> Since the clients must not have a direct dependency on the new packages
>> (since they were compiled without it), you could look into push the
>> dependencies out into the service and provide a "bigger" service that hides
>> the new dependencies, then only the service bundle would need the dynamic
>> import.
>>
>>   ->  richard
>>
> We did have the setup with the big service hiding these dependencies
> before. But this caused 'problematic' dependencies. Then the big service
> depends on packages imported in the templates. Whenever one of these was
> changed, and a refresh has been issued, the big service was refreshed and
> along with it all its clients. In our case we have lots of clients and this
> caused a cascade of restarting bundles and ended with nearly every bundle
> being restarted. That's the reason for this effort. The idea was to get rid
> of these dependencies and make the clients depend on what the use, such
> that the affected services would correcpond with their actualy requirements.
>

Then I think dynamic imports are about as good as it is going to get, 
since there really isn't a way to programmatically add imports to bundles.

-> richard


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@felix.apache.org
For additional commands, e-mail: users-help@felix.apache.org


Mime
View raw message