On 2010-05-11 15.20, Philippe Van Dyck wrote:
Rickard,
my own experience with osgi (a couple of years ago) was quite bad
regarding tools support (dev & prod environments).
After trying a couple of "bundles compositions" (including a very
interesting one mixing wicket & osgi) I went back to a simple maven
driven jetty basic servlet container.
Coupled with jrebel (and the maven jrebel plugin), any re-compiled class
is reloaded and if it doesn't work, just type enter in the maven
jetty:run and voilà, a nice and clean restart.
If your CI drives you private repository, you can provision complete
applications easily (i.e.: using profiles).
So if you want an up and running environment with reloading, a quick
start up time and easy reloading... it's the best solution I have
composed until now.
One problem is that I need to support plugins in my app. We, and other
developers, need to be able to extend the app. If we use OSGi we don't
need to reinvent that wheel, which seems tempting.
I'm trying it out now to see how it works. So far so good. Redeployment
by simply copying the jar-file into GlassFish seems easy enough. If I
can couple that with debugging and class reloading that is a decent
combo for both production and development.
/Rickard
_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev
