|Re: Lazy service activation in Gemini Blueprint [message #555262 is a reply to message #550846]
||Thu, 26 August 2010 02:48
| Costin Leau
Registered: February 2010
Seems we are talking about two different types of lazy here:|
OSGi bundle lazy - meaning the bundle is not active and no class loading is performed
bean/instance lazy - as in Spring sense, meaning the actual instance is not created yet.
The first is not supported in Spring DM/Blueprint since it's impossible to guarantee. For example, in order to register a ServiceFactory, one would have to know how to create a bean instance which means it would have to know how to create the instance (class loading included).
Additionally, many tools or libraries perform bundle scanning which automatically triggers class loading.
Further more, unless the service is registered, a bundle is likely to not ever get activated since there are no 'triggers' for that - unless somebody explicitly locates the bundle and loads an (existing) class, there is nothing in the service registry to pick on.
Hope this helps,
Powered by FUDForum
. Page generated in 0.01538 seconds