On 12/23/11 9:55 AM, 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.
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.
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
--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Weibo: willemjiang
