Hi Nuwan, According to the spec, If the bundle activation policy is lazy, then its state will be in "STARTING" once it passed the "RESOLVED" stage without encountering any issues. The state remains as "STARTING" until there is an event to load class from the this bundle space. Then only the state changes to "ACTIVE" once it has properly finished calling the bundle activator. This is known as the "On-Demand" activation.
So to answer your question, the first bundle's state will remain in "STARTING", until the second bundle calls/uses a class from it. This call will trigger the even to start the BundleActivator. Then the state will change to "ACTIVE" once BundleActivator's start method returns without any issues. BTW, we do not have this policy set for carbon related bundles (mostly). Are you working on dev-studio/eclipse project related bundles to observe this behaviour? Thanks, On Fri, Jun 26, 2015 at 4:59 PM, Nuwan Pallewela <[email protected]> wrote: > If a plug-in's Bundle Activation Policy is configured as "lazy", will > another plug-in which depends on it can use it if the current state of the > first plug-in is in RESOLVED state? Will it come to ACTIVE state because of > the second plug-In's invocation? > > -- > ---------------------------------------------------------- > > *Nuwan Chamara Pallewela* > > > *Software Engineer* > > *WSO2, Inc. * > *lean . enterprise . middleware* > > Email *[email protected] <[email protected]>* > Mobile *+94719079739 <%2B94719079739>* > *+94767100087 <%2B94767100087>* > > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Kishanthan Thangarajah* Associate Technical Lead, Platform Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com <http://kishanthan.wordpress.com>* Twitter - *http://twitter.com/kishanthan <http://twitter.com/kishanthan>*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
