Re: [equinox-dev] One bundle does not auto start in Servlet Bridge

[David Cao <govelogo@xxxxxxxxx>]

I seemed to have solved the problem by switching from "masterconsole.web@start" to "masterconsole.web.1.0.1.jar@start". But this is annoying if I have to update every time I release a new bundle.

Is there a better way? and why this happens in the first place? (the problem seems happen in both Win 7 64bit and Redhat 6 win64 VM) ... thanks!!

On Wed, Jul 30, 2014 at 8:04 PM, David Cao <govelogo@xxxxxxxxx> wrote:

Hello there,

I have two bundle configured to auto start when Servlet Bridge project start. Here is my /WEB-INF/eclipse/configuration/config.ini,

osgi.bundles=org.eclipse.equinox.common@2:start, org.eclipse.update.configurator@start, org.eclipse.equinox.http.servletbridge@start, org.eclipse.equinox.http.registry@start, org.apache.felix.webconsole@start, masterconsole.web@start, masterconsole.persistence@start

osgi.bundles.defaultStartLevel=4

However, materconsole.persistence always starts fine; but masterconsole.web always shows Resolved; and I have to manually start it in Felix console. (masterconsole.web is a converted from a .war archive)

Here is the manifest of the masterconsole.web bundle,

Manifest-Version: 1.0

Bundle-ManifestVersion: 2

Bundle-Name: masterconsole.web

Bundle-SymbolicName: masterconsole.web

Bundle-Version: 2.0.0

Bundle-Activator: masterconsole.web.Activator

Bundle-ClassPath: .,

 WEB-INF/classes,

 WEB-INF/lib/...

Import-Package: mc.console.api,

 javax.servlet,

 javax.servlet.http,

 org.osgi.framework;version="1.3.0",

 org.osgi.service.http;version="1.2.0",

 org.osgi.util.tracker;version="1.3.1"

Does anyone have such experience before? thanks!!!

David