Edward Yakop wrote:
On Mon, Mar 30, 2009 at 11:43, Rickard Öberg <[email protected]> wrote:
That's nice! Can you give some detail on what this means, and what features
it would enable?
It would enable qi4j application to be deployed in OSGi container.
What's the possibilities?
The possibilities are:
1. To reload module/layer/application on runtime.
We are mainly talking about reloading implementation, right? Since the
bindings would require restart of app?
As already outlined in a previous post though, it's entirely possible to
have one module create another app as "plugins", which can be restarted
without restarting the encapsulating application. Maybe this would be
the pattern to use here.
2. Import OSGi services to qi4j application and export Qi4j services to OSGi.
Very nice!
What are the limitations?
I'm not sure about the limitations.
We probably need to attempt 1 and create/port sufficient complex app
to realize this.
Ok, gotcha.
I am personally very interested in exploring OSGi possibilities in the
StreamFlow app, both on client and server, so this is good news!
:)
It was a coincidence :) I upgraded pax-wicket to use pax-exam 0.3.0,
and remembered that
Qi4j is using deprecated pax-drone 0.2 :)
Well, coincidence or not, it's nice to hear that it works :-)
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
