Hi Jörg, I understand your view. However, as there is no support for scopes in OSGi, the reasonable approach would be to import ALL dependencies for all Neo4j code. That would require quite substancial numbers of bundles for e.g. the enterprise edition that pollute the Bundle Space for the whole system.
Also, it seems every OSGi setup has its own granularity level. E.g. some want to use their own Lucene bundle, some installations prefer the Neo4j ones, some like JTA as its own bundle, etc etc. So for the time being I thought a template default setup would be a good start, as refactoring the Java Service Loader to be fully OSGi aware seems very big to get to a stable state across all frameworks and systems. The template is just one pom.xml at https://github.com/neo4j/neo4j-osgi/blob/master/bundle/pom.xml and the resulting "default" bundle could easily be published. Do you think fine grained atomic bundles instead of a sueprbundle template that is adaptable would be really generic? Secondly, I think the request for an injection-based initialization method for index providers sounds good. Could you add a lighthouse ticket at http://neo4jdb.lighthouseapp.com/projects/77609-neo4j-community/tickets or add you requests to http://neo4jdb.lighthouseapp.com/projects/77609/tickets/3-osgi-environments-not-starting-lucene ? Cheers, /peter neubauer GTalk: neubauer.peter Skype peter.neubauer Phone +46 704 106975 LinkedIn http://www.linkedin.com/in/neubauer Twitter http://twitter.com/peterneubauer http://www.neo4j.org - Your high performance graph database. http://startupbootcamp.org/ - Öresund - Innovation happens HERE. http://www.thoughtmade.com - Scandinavia's coolest Bring-a-Thing party. On Wed, Jul 20, 2011 at 1:55 PM, Jörg Richter <j...@deepamehta.de> wrote: > > Thanks for replies! > > Yes, the super bundle approach (putting *all* neo modules and *all* their > dependencies in one bundle) works in principle. But to be a deployable > solution ... > 1) it must exist in the Maven repo and be on a par with the Neo4j release > 2) A configuration mechanism is required to choose the modules actually needed > > To abandon the super bundle approach and as long as the original problem > (Java Service Loader and OSGi) is not solved: how about bringing back the > old-style (serviceloader-less) indexing API as an *alternate* entry point? > > This would allow thousands of OSGi users to use Neo4j > 1.2 and they would > love it. > > Cheers, > Jörg > > > > On Jul 20, 2011, at 9:20, Peter Neubauer wrote: > >> Could you please try the OSGi neo4j super bundle built in github / neo4j / >> Neo4j - osgi / bundle? >> >> Fine grained bundle deployment interferes with the java service loader which >> only looks in its own classpath. > > _______________________________________________ > Neo4j mailing list > User@lists.neo4j.org > https://lists.neo4j.org/mailman/listinfo/user > _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
