Posted by jfarcand
on May 15, 2008 at 1:23 PM PDT
Grizzly has OSGi bundles available for a while, but we haven't made any noise about it yet. Since OSGi is the current buzz, let's the monster enter the buzz circus...
Grizzly has OSGi bundles available for a while, but we haven't made any noise about it yet to let the spotlight on GlassFish v3 . Since OSGi is the current buzz, let's the monster enter the buzz circus...
Since release 1.7.0 (we are now shipping 220.127.116.11), Grizzly ships with jar file manifests that include appropriate OSGi bundle information. This means that you can import the Grizzly jars into an OSGi framework and use them, for example, to build a I/O application using the framework classes , to build a static Web Server or a Comet messages bus. Those jars are currently self-contained for the reason that you can use them for testing using a simple command like:
java -jar [bundle-name] -p [port] -a [war|jar|directory location] [Component_name]
As an example, you can:
% java -jar grizzly-messagesbus-webserver-18.104.22.168.jar -p 8080 -a jmaki-messagesbus-demo.war
which start a simple Comet messages bus (I will soon blog about this new module). As usual, let us know what you think about those OSGi bundles, if they are ok or not, as none of us are OSGi expert. You can download those OSGi bundles from here ...
technorati: grizzly glassfish comet