Hi,
Not sure we should do it for JAXB(and also jaxws). As in most case the
jaxb/jaxws api(as in JDK6 it use jaxws/jaxb 2.1 but in most case we
need use 2.2, and also the SPI mechanism of jaxws doesn't work in OSGi
container) from jdk isn't much useful and so in Servicemix we shipped
jaxb
hmm, OK,
does it really prevent us from actually fixing the version of JAXB in
the jre property in conjunction with what Andreas just suggested?
I'd really favor changing the jre properties (I actually did that on a
project fixing my issues with jaxb this way) and providing functional
features
On Tue, Aug 30, 2011 at 13:17, Achim Nierbeck bcanh...@googlemail.comwrote:
hmm, OK,
does it really prevent us from actually fixing the version of JAXB in
the jre property in conjunction with what Andreas just suggested?
I'd really favor changing the jre properties (I actually did that on a
I don't think hack jre.properties can support jaxb2.2 and create a
default feature which contain smx jaxb bundles should be the solution.
But I have little concern that this will make karaf more like smx and
this actually is against our initial idea that keep karaf as a simple
general
On Tue, Aug 30, 2011 at 13:40, Freeman Fang freeman.f...@gmail.com wrote:
I don't think hack jre.properties can support jaxb2.2 and create a default
feature which contain smx jaxb bundles should be the solution.
But I have little concern that this will make karaf more like smx and this
Just to get this right,
for JAXB if someone needs a JAXB 2.2. he needs to provide it by
himself (or we can offer some nice features for it +1)
but for the included jre JAXB which causes all kinds of issues if you
even provide your own JAXB 2.2. I think it's a good solution
to set the version to
First of all, the default jre export package version is 0, so if
customer bundle import such package but not specify the version, then
it always work, that's why I said we generally needn't specify the jre
export package version.
And the main reason smx doesn't use the jaxb/jaxws api from
The entire problem is that you still have to manipulate the jre.properties.
The problem here is because of double-exports/imports. I'm curious if
setting the xml exports to 2.1 fixes the problem. I'll give it a shot
tomorrow
Kind regards,
Andreas
On Tue, Aug 30, 2011 at 14:14, Freeman Fang
the one thing about the JAXB running as version 0 is that (at least
when running with equinox it used to be that way) what ever version
you used or provided by yourself it still wouldn't work out since
always the one with 0 was used :(
2011/8/30 Andreas Pieber anpie...@gmail.com:
The entire
Hi,
This commit[1] also do same for JDK1.7.
I'd say other JDK API are quite stable but javax.annotation is a
little bit different so several other bundles(such as activemq, you
can get more details from [2]) which are popularly used in KARAF are
explicitly specify javax.annotation import
10 matches
Mail list logo
