On Friday, December 23, 2011 12:13:53 PM Willem Jiang wrote: > As I know you can't run the CXF application on the pure karaf without > changing the jre.properties. > There are some work need to be done as well as some camel components. > It is really depends on what we want karaf to be. > > The change of apache-camel feature which doesn't install the specs api > by default just wants to support different customer version of karaf at > the same time. > > The only inconvenience is that the user need to install the specs > feature by default, it is easy to do by change the > org.apache.karaf.features.cfg file to update the boot feature. > > If we install the feature by default, people will need to do lots of > work to hack apache-camel feature if he wants to use those package from JRE.
Which *I'm* quite OK with. I'd much rather have the default be the versions of the various technologies that we test with and know work. As another example, we NEED to have woodstox picked up. The way the StaxConverter uses the factories is not thread safe if using the in-JDK stax implementation. (yes, that could be considered a bug in Camel) Again, we need to provide the most stable setup out of the box so when issues are reported, we will have at least some idea of what their setup is. Dan > > Dan > > > >> On Fri Dec 23 07:53:07 2011, Christian Müller wrote: > >>> May it's a stupid idea, but if an OSGI containder decide to hide > >>> some > >>> packages from the JRE (for good reasons), shouldn't it install the > >>> bundles by default which provides the hidden packages so that we can > >>> trust the javax.xml.xxx packages are available - via the JRE or a > >>> bundle... > >>> > >>> Best, > >>> Christian > >>> > >>> Sent from a mobile device -- Daniel Kulp dk...@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com
