I have had big problems getting stax + jaxb as bundles working in karaf/osgi and thought the entire karaf-activator stuff was because guillaume had determined that it was impossible due to conflicts with xalan. I haven't seen any documentation on karaf-activator yet or the problems it's intended to solve. Maybe this could be remedied before we try for another solution to the same problem?
Another possibility is for camel and cxf to supply kars that when installed overwrite jre.properties. This doesn't require any karaf modifications. -1 until this is explained better. thanks david jencks On Dec 26, 2011, at 7:04 AM, Jean-Baptiste Onofré wrote: > Hi all, > > We have currently an issue in Camel and CXF with the default jre.properties > and some exported packages (like JAXB, etc). > > Currently, by default, the jre.properties exports all packages from the JRE. > > I would like to propose a new approach: > 1/ remove packages with problem by default from the jre.properties > 2/ add a set of Karaf features (in bootFeatures by default) to install > bundles providing the packages (JAXB, etc) > > It's a quick workaround for next Karaf 2.2.6 and Karaf 3.0. > > We can find a more elegant solution. I have some solutions in mind: > - new properties in the jre.properties to define an "override" flag > - add a KARAF-INF/* files to define some behaviors (like overriding system > packages) > > Feel free to propose your ideas for this problem. > > Please: > [ ] +1 to remove the packages from the jre.properties and provide a set of > Spec/API features in Karaf > [ ] 0 > [ ] -1 for that (please provide arguments) > Ideas (if you have ;)): > > Thanks > Regards > JB > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com
