Gang,
hope you enjoyed the holidays ?
I wanted to call for a new Pax sub project called TinyBundlles.
Its a quite small library that i found very joyful to use myself in
combination with pax exam (but not limited to that).
You can define and create (tiny) bundles using java api, get inputstreams
from the final bundle and do all kinds of funny things.
compared to traditional built-by MVN/PDE bundles this makes "trying things
out" much more entertaining.
Basic usage:
newBundle()
.set( Constants.BUNDLE_SYMBOLICNAME, "MyFirstTinyBundle" )
.set( Constants.EXPORT_PACKAGE, "org.ops4j.pax.tinybundles.demo" )
.set( Constants.IMPORT_PACKAGE,
"org.ops4j.pax.tinybundles.demo,org.osgi.framework" )
.set( Constants.BUNDLE_ACTIVATOR, MyFirstActivator.class.getName() )
.addClass( MyFirstActivator.class )
.addClass( HelloWorld.class )
.addClass( HelloWorldImpl.class )
.build( asStream() )
So, you define metadata (manifest) plus pull-in resources from current
classpath. Your bundle(s) will be a subset of your ("traditional" =non osgi)
fat classpath like you have in unit tests.
Currently you are 100% of your own meaning you define the whole manifest
which gives max. felixibility+control and is okay if your bundles keep being
tiny.
All kinds of "helpers" (bnd) can be stacked on top of cause if wanted.
Usecases (in exam, where i played most with it):
- testing extenders (did so in a corporate project (..)). Good kickstart for
SpringDM support maybe.
- load tests where you probably want to make your system very busy
Question: is this totally sick ? Because i enjoyed it quite much (did i told
already?) which could be a bad sign though ;)
Otherwise i will move it from my lab to projects asap.
--
Toni Menzel
Software Developer
Professional Profile: http://www.osgify.com
t...@okidokiteam.com
http://www.ops4j.org - New Energy for OSS Communities - Open
Participation Software.
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general
