[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Creating and Starting a BundleActivator when the framework launches


Note that this bug does not cover for Simon's original need.




Thomas Watson <tjwatson@xxxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx

04/10/2006 10:13 AM

Please respond to
Equinox development mailing list

To
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>
cc
Subject
Re: [equinox-dev] Creating and Starting a BundleActivator when the        framework launches







> Another area of interest here is the conversation I had with Tom Watson at
> EclipseCon. We were brainstorm ways to get Declarative Services registered
> for bundles which were not started. While there are many details to work
> out, the basic idea was for the framework to mark lazy start bundles in
> the STARTING state rather than just the RESOLVED state. This would (a)
> allow them to still avoid having a class loader and (b) allow SCR to
> register their declarative services since they are technically started.
> More thinking is needed here though. These bundles woudl stay in the
> STARTING state until a class was loaded from them. This could occur for
> any reason including SCR trying to load the implementation class for a
> declarative service once it was used by some other bundle. This would
> allow bundles to be installed and provide service without having to be
> explicitly started. I think this is something interesting to pursue for
> 3.3.


I opened bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=135885

to investigate this for 3.3.


Tom.


>
> BJ Hargrave
> Senior Technical Staff Member, IBM
> OSGi Fellow and CTO of the OSGi Alliance
> hargrave@xxxxxxxxxx
> Office: +1 407 849 9117 Mobile: +1 386 848 3788
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev