On Nov 10, 2009, at 7:59 AM, Rick McGuire wrote:
There are two subprojects in the jaxws plugin that I'm having
trouble building, and I can't figure out why. The cause of the
failure is a resolution failure trying to resolve the javax.jws
package, version 2.0. These classes are contained in the geronimo-
ws-metadata specs bundle, and should be there. Running the build
with the -X option does not show any sign that this bundle is
getting installed and started before the error. I've tried adding
this as dependency in every pom I could think of to force this to be
loaded first and nothing appears to have made a difference. That
bundle just doesn't seem to get loaded. The manifests look good in
all cases, but it just doesn't appear to load.
I also tried specifying a version in the karaf config.properties on
the javax.jws packages, but that didn't make any difference either.
There's obviously something going wrong with how the dependencies
are processed here, but I can't seem to spot what's messing up.
Everything looks like what I'd expect to see when I use
dependency:tree.
For now, I've just commented these two items out so they won't
build, but this is going to need to be solved eventually.
I suspect these classes are also in the jvm. Maybe the situation is
similar to the one for javax.transaction where some classes come from
the jvm and some from the spec jar? The mysterious fix for that seems
to be, in etc/config.properties from framework/config/karaf-framework/
src/main/resources/filtered-resources/etc/config.properties
org
.osgi
.framework
.bootdelegation=sun.*,com.sun.*,javax.transaction,javax.transaction.*
and
javax.transaction; javax.transaction.xa; partial=true;
mandatory:=partial, \
Might be worth experimenting with anyway.
david jencks
Rick
