My .2 is that I haven't really used this stack commercially ever without at least some of the CXF features, I know that cxf is large, sure but since the cxf defaults when setup right provides better than jre settings for quite a few things, faster stax parsing etc etc.
I kinda sorta wanna see CXF as a core library in this little corner of the Apache world, since we already see karaf and features as a "default" I don't see why complicated options would be good. I think at the very very very least that Karaf should have JAXB and Woodstox setup out of the box… Hunting Jaxb problems while good money isn't really making for happy customers. On Dec 22, 2011, at 6:55 PM, Daniel Kulp wrote: > On Friday, December 23, 2011 8:57:22 AM Willem Jiang wrote: >> That is why we doesn't install xml-spec-api feature by default. >> But current Karaf 2.2.4 doesn't do it by default :( > > Honestly, I really think we should restore the specs and jaxb-impl into the > defaults. Right now, we're in a state where to run some things, you can use > some settings, but to run other things, you need to edit settings and > restart. > It's basically completely different instructions depending on what you want > to > do with Camel and which components you want to start. We don't have a > single > set of "If you want to run Camel in OSGi, do *this*". I personally think > that is confusing for me, let alone users. > > > > 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
