Brett, correct me if I’m wrong, but isn’t there a difference in making some library *work* in an OSGi environment and making that library *naturally fit well* in an OSGi-enabled application? For example, making the JAR’s be OSGi bundles is easy and technically makes it possible to deploy a JAR into an OSGi env, but that’s not where the payoff is. IIUC what you really want is a BundleActivator or Declarative Services [1] so that the library’s components are readily available in a naturally-OSGi way.
[1] http://blog.knowhowlab.org/2010/10/osgi-tutorial-4-ways-to-activate-code.html On Dec 6, 2013, at 7:30 AM, Mircea Markus <[email protected]> wrote: > + infinispan-dev > > Thanks for offering to look into this Brett! > We're already producing OSGi bundles for our modules, but these are not > tested extensively so if you'd review them and test them a bit would be great! > Tristan can get you up to speed with this. > > >>> Sanne/Galder/Pete, >>> >>> Random question: what's the current state of making Infinispan OSGi >>> friendly? I'm definitely interested in helping, if it's still a need. >>> This past year, I went through the exercise of making Hibernate work well >>> in OSGi, so all of challenges (read: *many* of them) are still fairly fresh >>> on my mind. Plus, I'd love for hibernate-infinispan to work in OSGi. >>> >>> If you're up for it, fill me in? I'm happy to pull everything down and >>> start working with it. >>> >>> Brett Meyer >>> Software Engineer >>> Red Hat, Hibernate ORM >>> >> > > Cheers, > -- > Mircea Markus > Infinispan lead (www.infinispan.org) > > > > > > _______________________________________________ > infinispan-dev mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/infinispan-dev _______________________________________________ infinispan-dev mailing list [email protected] https://lists.jboss.org/mailman/listinfo/infinispan-dev
