Eclipse Community Forums: Virgo » Plan with CXF DOSGi 3.1.6 fails to start

Help

Home

Home » Eclipse Projects » Virgo » Plan with CXF DOSGi 3.1.6 fails to start

Show: Today's Messages :: Show Polls :: Message Navigator

Plan with CXF DOSGi 3.1.6 fails to start [message #1739125]

Wed, 27 July 2016 15:44

Bill Mair

Messages: 72
Registered: July 2009

Member

This is my first attempt at using a Virgo plan and I'm failiing miserably Rolling Eyes

First it complained about some of the version entries not being numeric:

name="org.apache.servicemix.bundles.jaxb-impl" version="2.2.11_1"
with a file called: org.apache.servicemix.bundles.jaxb-impl-2.2.11_1.jar

So I change the file names by replacing the _ with a . (which is also what is in the bundle manifest: Bundle-Version: 2.2.11.1).

All good, the result is the attached plan, now I'm getting the following error on the very first bundle:

[2016-07-27 16:39:08.738] ERROR fs-watcher                   org.eclipse.virgo.medic.eventlog.default                         DE0003E Install failed for plan 'cxf-dosgi-plan' version '1.8.0'.

[2016-07-27 16:39:08.738] INFO  fs-watcher                   System.out                                                        org.eclipse.virgo.nano.deployer.api.core.DeploymentException: Deployment of plan 'cxf-dosgi-plan' version '1.8.0' in scope 'null' failed: bundle 'geronimo-osgi-registry' in version range '[1.1.0, oo)' not found

I copied all the JARs from the DOSGi 1.8.0 release to ext/usr and the file "geronimo-osgi-registry-1.1.jar" exists.

The contents of the bundle also states Bundle-Version: 1.1

Is the naming incorrect? Have I misunderstood plans?

Attachment: apache-cxf-dosgi.plan
(Size: 4.20KB, Downloaded 305 times)

Report message to a moderator

Re: Plan with CXF DOSGi 3.1.6 fails to start [message #1739129 is a reply to message #1739125]

Wed, 27 July 2016 15:49

GianMaria Romanato

Messages: 57
Registered: November 2015

Member

Hi Bill,

Maybe "geronimo-osgi-registry" is the bundle name, not the symbolic name?
The bundle name attribute in the plan is not expected to contain the Jar file name, but rather the symbolic name of the bundle.

With respect to the version, you can safely omit it as it is not mandatory, as long as you don't have multiple versions of the same bundle in the repository folder(s).

GianMaria.

Edited: rephrased a sentence to make it easier to understand.

[Updated on: Wed, 27 July 2016 15:51]

Report message to a moderator

Re: Plan with CXF DOSGi 3.1.6 fails to start [message #1739135 is a reply to message #1739129]

Wed, 27 July 2016 16:02

Bill Mair

Messages: 72
Registered: July 2009

Member

Perfect! It was the bundle symbolic name that was causing the problem.

I've had to change all of the short names to the fully qualified symbolic names it the plan is now "ACTIVE".

Thanks!

Report message to a moderator

Re: Plan with CXF DOSGi 3.1.6 fails to start [message #1739198 is a reply to message #1739125]

Thu, 28 July 2016 09:40

Bill Mair

Messages: 72
Registered: July 2009

Member

The plan starts and all the defined bundles are resolved and running.

I haven't included CXF's jetty bundle as I don't want that starting up. I have configured SPNEGO single sign on in Virgo's tomcat and I don't want to have to manage 2 web servers.

I registered a service whose interface is annotated with the javax.jws annotations.

And in the props I have also added the following values:

service.exported.interfaces = my.interface.Name
service.exported.configs = org.apache.cxf.ws

context.registerService( my.interface.Name.class, myImpl, props );

Everything works but I must still be missing something.

It doesn't look like CXF registers itself with tomcat as a servlet and I don't see anything in the logs that would point to anything in that direction.

Can some kind soul point me in the right direction please?

Report message to a moderator