Actually, shouldn't Pax TinyBundle (hate this name) be part of Pax
Swissbox? Swissbox is our place for utilities for OSGi and I see Pax
TinyBundle (hate this name) just an utility.
So, WDYT? move it to swissbox?
Did I mention that I hate the name? :)
On Tue, Apr 14, 2009 at 4:21 PM, Alin Dreghiciu <adreghi...@gmail.com>wrote:
> I find the idea quite useful. But I would not make a full blown Pax
> project out of it. Yet.
> I suggest adding this as an Pax Exam module. Keep it in such a way
> that it does not depend on PAx Exam itself. Then if we see traction
> just take it out and make a project out of it.
>
> So, +1 to move it out of your lab to a Pax Exam module.
>
> On Tue, Apr 14, 2009 at 11:04 AM, Toni Menzel <t...@okidokiteam.com>
> wrote:
> > 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
> >
> >
>
>
>
> --
> Alin Dreghiciu
> http://www.ops4j.org - New Energy for OSS Communities - Open
> Participation Software.
> http://www.qi4j.org - New Energy for Java - Domain Driven Development.
> Looking for a job.
>
--
Alin Dreghiciu
http://www.ops4j.org - New Energy for OSS Communities - Open Participation
Software.
http://www.qi4j.org - New Energy for Java - Domain Driven Development.
Looking for a job.
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general
