On Dec 18, 2012, at 5:53 PM, Sven Zethelius <[email protected]> wrote:
> I've been doing a quick check to start upgrading an application from 2.4.X to > 2.7.X that is using OSGi. Step 1 was just determining which jars are needed > to satisfy OSGI startup. I'm starting by just looking through the > MANIFEST.MF of cxf-bundle to see what packages are require (not > resolution:=optional). > > New to the list of required packages are: > org.apache.lucene.document, > org.apache.lucene.index, > org.apache.lucene.search > > Are these really "required" for minimum functionality to startup the bundle? > Looking at uses, it seems isolated to org.apache.cxf.jaxrs.ext.search. > > Is this a bug? Should these packages be resolution:=optional That's definitely a bug. HOWEVER, if upgrading from 2.4.x to 2.7.x, it is STRONGLY recommended that you not use the big cxf-bundle. There are a lot of new OSGi related features that will not work if you use the big bundle. Instead, use the small individual modules. Starting with 2.6.0, each module is a proper OSGi bundle and can be installed in the OSGi runtime by itself. Each module has it's own set of imports, etc… that are needed for that module. By using the smaller modules, you can create a much smaller runtime, faster startup, etc… and a more reliable runtime as there are significantly less "optionals" that may need to be resolved. Also, several of the individual bundles have special Activators that will activate additional features that will be unavailable in the big bundle. For example, using the configuration admin stuff to configure HTTP conduits or jetty ports will not work. -- Daniel Kulp [email protected] - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
