Yeah, I agree with Guillaume here.
Karaf should be a lightweight general purpose OSGi container, We
should avoid tweaking for any particular use cases.
There're already several other projects based on Karaf, which can
handle very different use cases with a wide range, to support those
use cases the configuration is different or even conflict, that why we
should leave other projects which are based on Karaf to take care of
it. IMO Karaf should focus on as general as possible, but not aim to
support every particular use cases out-of-box.
My 0.02 cents.
Freeman
On 2011-12-27, at 上午7:11, Guillaume Nodet wrote:
On Mon, Dec 26, 2011 at 21:09, Christian Schneider
<[email protected]> wrote:
I am +1 for not exporting the packages by default in the system
bundle.
In earlier versions of karaf, that was the case, but people complained
that the behavior was not intuitive.
People using karaf should not have to worry too much when willing to
use features provided by the JRE.
So I'm -1 on any solution does not provide access to the JRE by
default.
I'd also like to avoid tweaking the karaf container for any particular
use case, and deploying cxf and camel is just one use case.
I also have an idea how we could create an environment for people
who do not
want the improved bundles.
I propose that we provide two (sets of) features:
1. jaxb, stax, ... from jre
These are just fragment bundles to the system bundle that export the
packages. So by installing these bundles
you get the current behaviour of karaf
2. improved jaxb, stax, .. like used for servicemix, cxf, camel
These will make cxf and camel behave like expected
The reason why I prefer this aproach over the current setup of simply
exporting the packages from the system bundle is that it makes
installing cxf and camel much easier and at the same time also
allows people
to use "pure OSGi" like Guillaume wrote.
Christian
Am 26.12.2011 16:04, schrieb Jean-Baptiste Onofré:
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
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
--
------------------------
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com
---------------------------------------------
Freeman Fang
FuseSource
Email:[email protected]
Web: fusesource.com
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
