On 4/22/10 11:40, Elliot Huntington wrote:
Hi:
I just started researching OSGi this past week so I'm very new to it
and have never developed an application using it. But I am very
interested in learning this technology. In my research I've learned
that the different bundles can communicate with each other by
publishing/consuming services to/from the service registry. I am
confused though how this process works.
For example I want to create a bare bones OSGi GUI application. I want
this application to only manage the lifecycle of the gui (open the
main frame and handle the shutdown/closing of the program). Then, I
would like to create other projects (bundles) that provide all the
features for this application via plugins. I'm thinking that the best
way to do this would be to create the main GUI application with an
instance of embedded Felix.
I don't think you need an embedded framework instance...you could just
as easily create the main GUI as a bundle and probably the better
approach. Check out the paint program example, which works both ways:
http://felix.apache.org/site/apache-felix-application-demonstration.html
-> richard
Given this scenario, how would the different pluggins/bundles know how
to modify the main GUI and add functionality to it? Does the GUI
itself need to provide hooks into it and if so how does it do that?
If any of you have any example code or tutorials you could point me to
I would appreciate it.
Thanks,
Elliot
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@felix.apache.org
For additional commands, e-mail: users-h...@felix.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@felix.apache.org
For additional commands, e-mail: users-h...@felix.apache.org
