Christian
Thanks quick reply very much!
> In general the main question is: What do you want to achieve with your
> described agent. What is the actual problem you are facing?
Well, I will say detailed background as following:
Asumming there is an application server made up many modules or OSGi
bundles, these bundles are divided into two catogories, one is developed
by the application server team,called system bundle and the other is
developed by the third part.
For system bundles, the application server has itself module starting
rule, Eg. by defining some annotations in some classes, then, runtime
can scan these annotations and while kernel is starting, it can start
these system bundles adaptivly.
However, for the third part bundles, we will have no chance or better
way liking system bundles to start them adaptivly.
If defining some metadata or rules in Spec, maybe we will have better
general way to unify such behavior.
Maybe I still have not said clearly. I am sorry...
Thanks
Tang
Christian Schneider wrote:
What you describe sounds a lot like the extender pattern. Many
frameworks like Declarative Services or Blueprint use this pattern.
I would not use it for start levels though. If you look at the
frameworks they typically calculate the start order by your defined
dependencies like service dependencies.
This is much more robust than start levels.
I would also propose to just choose one of the existing frameworks
rather than creating your own one.
In general the main question is: What do you want to achieve with your
described agent. What is the actual problem you are facing?
Christian
On 19.12.2013 06:55, Tang Yong wrote:
Hi
I have a question about bundle starting since I have started OSGi
related development.
Whether considering bundle adaptive starting or not?
Eg.
Making an agent bundle, after installed bundles into OSGi runtime, the
agent bundle can scan current installed bundles and based on some
rule(annotations related to start level, new metadata for adaptive
starting...), adaptivly starting those bundles meeting up the rule.
Want to listen your ideas.
Best Regards!
Tang
--
－－－－－－－－－－－－－－－－－－－－－－
Tang Yong
Senior Engineer
GlassFish Committer (OSGi & OSGi-JavaEE)
OSGi Alliance Supporter
Blog: http://osgizone.typepad.com/tangyong/
Nanjing Fujitsu NanDa Software Tec CO.,LTD
http://www.fujitsu.com/cn/fnst
Tel: +86-25-86630566-8310
Fax: +86-25-83317685
－－－－－－－－－－－－－－－－－－－－－－
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
