What I mean is that I don't want Karaf to turn into a container tweaked for deploying CXF or Camel at the expense of *basic* OSGi applications.
A lot of people want to use JAXB and are happy to use the one provided by the JRE. That' should be the default behavior. Karaf should if possible provide a way to deploy the needed bits for Camel and CXF without modifications, but if you want/need a custom container, you need a custom project. I don't really see Karaf shipping a different xalan / xerces implementation, because CXF might need it in some cases or ship woodstox by default. That sounds like a custom CXF distribution of Karaf and should be done in CXF or elsewhere (even in a karaf subproject), but not in the main distribution. Likewise, solving SAAJ problems only affect a small portion of our user base, so we shouldn't tweak the container for a single use. I don't care if the solution to those problems come from ServiceMix, CXF, Camel or whatever project. Even from Karaf. But I don't want the basic operations to not work anymore. I'll resume my work on the enhanced specs and those *could* be included by default in Karaf if we think it's desirable. They should hopefully fix most of our problems with specs / packages. Don't get me wrong, I'd like to have those problems fixed, but at the correct location and not turning Karaf into a tweaked container for CXF or Camel or ActiveMQ or any other project. On Tue, Dec 27, 2011 at 04:05, Daniel Kulp <[email protected]> wrote: > On Monday, December 26, 2011 8:13:39 PM Guillaume Nodet wrote: >> Once again, a lot of karaf users just want OSGi. People who want to deploy >> cxf or camel should be targetted to ServiceMix instead. > > This is where I STRONGLY disagree with you. If people want to deploy CXF or > Camel into OSGi, we should be working on making that easier and work better if > at all possible, not point them off to another project. Installing CXF > should just be a features:addurl and a features:install. People may already > have OSGi based applications that they want to add CXF or Camel services into. > They definitely shouldn't be required to switch to ServiceMix for that. > > I'm hoping your activator idea can really get us there. If that works well, > then I'm hoping the above can really become a reality. > > Dan > > > >> >> On Monday, December 26, 2011, Jean-Baptiste Onofré <[email protected]> wrote: >> > Agree Ioannis, >> > >> > I think that 95% of the users don't know the issue, the jre.properties, >> >> etc :) >> >> > They just want to use Camel or CXF directly in Karaf. >> > >> > Regards >> > JB >> > >> > On 12/26/2011 04:13 PM, Ioannis Canellos wrote: >> >> Is there any chance that there are users that prefer the jre packages >> >> ? >> >> >> >> From what I understand most Karaf users will not use them at all, >> >> but I >> >> am >> >> >> not sure about it. >> >> >> >> If most of our users, will disable them anyway, I see no reason not >> >> doing it ourselves ( +1 ). >> > >> > -- >> > Jean-Baptiste Onofré >> > [email protected] >> > http://blog.nanthrax.net >> > Talend - http://www.talend.com > -- > Daniel Kulp > [email protected] - http://dankulp.com/blog > Talend Community Coder - http://coders.talend.com -- ------------------------ Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com
