[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Bug in "Run As Equinox"


A simple test could be:
1. Add eclipse 3.2.1 plugins folder as target platform
2. Add org.ops4j.pax.logging.api
   to the plugins folder.
3. Set up a run as eclipse application, and set the program to run:
4. In plugins tab folder include org.ops4j.pax.logging.api
5. In arguments tab, in program argument add
    -console 5000
5. Click Apply
6. Click Run

Once the application started.

7. Telnet 5000
8. Execute
osgi> sl
Framework Active Start Level = 6

9. Execute
osgi> sl 58
Bundle 58 Start Level = 4

Note: Bundle 58 = org.ops4j.pax.logging.api_0.9.4
10. To prove that logging api can be started. Execute
osgi> start 58

osgi> bundle 58
update@plugins/org.ops4.pax.logging.api-0.9.4.jar [58]
  Id=58, Status=ACTIVE      Data Root=C:\Documents and Settings\efy\Desktop\radman\org.eclipse.osgi\bundles\58\data
  No registered services.
  No services in use.
  Exported packages
    org.ops4j.pax.logging; version="0.9.4"[exported]
    org.knopflerfish.service.log; version="1.1.0"[exported]
  Imported packages
    org.osgi.framework; version="1.3.0"<System Bundle [0]>
    org.osgi.util.tracker; version="1.3.2"<System Bundle [0]>
    org.osgi.service.log; version="1.3.0"<update@plugins /org.eclipse.osgi.services_3.1.100.v20060601.jar [35]>
    org.ops4j.pax.logging; version="0.9.4"<update@plugins/org.ops4.pax.logging.api-0.9.4.jar [58]>
    org.knopflerfish.service.log; version=" 1.1.0"<update@plugins/org.ops4.pax.logging.api-0.9.4.jar [58]>
  No fragment bundles
  Named class space
    org.ops4j.pax.logging.api; bundle-version="0.9.4"[provided]
  No required bundles

Edward Yakop

On 10/12/06, Thomas Watson <tjwatson@xxxxxxxxxx> wrote:

OK, open a bug against Equinox->Framework.  Preliminary tests with my own bundles do not seem to reproduce the problem.  Please detail the steps to reproduce in the bug report.  Thanks.


"Niclas Hedhman" <niclas@xxxxxxxxxxx>
Sent by: equinox-dev-bounces@xxxxxxxxxxx

10/11/2006 08:33 PM

Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>

"Equinox development mailing list" <equinox-dev@xxxxxxxxxxx>

Re: [equinox-dev] Bug in "Run As Equinox"

Some preliminary checks;

26 ACTIVE org.eclipse.ui.workbench_3.3.0.I20060921-0010
27 RESOLVED org.eclipse.ui.workbench.texteditor_3.3.0.v20060920-1200
28 RESOLVED org.ops4j.pax.logging.api_0.9.4
29 RESOLVED org.ops4j.pax.logging.log4j_0.9.4
30 RESOLVED org.ops4j.pax.logging.service_0.9.4
31 ACTIVE org.ops4j.pax.radman.client_1.0.0
32 RESOLVED org.ops4j.pax.radman.client.api_1.0.0
33 RESOLVED org.ops4j.pax.radman.client.cache_1.0.0
34 RESOLVED org.ops4j.pax.radman.client.cache.ui_1.0.0
35 RESOLVED org.ops4j.pax.radman.client.console_1.0.0

osgi> sl
Framework Active Start Level = 6
osgi> sl 28
Bundle 28 Start Level = 4

Bundle 28 has no Imports and no BundleActivator. No exceptions or other errors are output.

To me this looks more like a Equinox bug than a PDE bug...


On 10/12/06, Niclas Hedhman < niclas@xxxxxxxxxxx> wrote:

On 10/11/06, Thomas Watson <tjwatson@xxxxxxxxxx > wrote:

That syntax should be fine.  It tells the bootstrap code (in EclipseStarter) to mark the bundle for persistent start and set its start-level to the value specified by the property  osgi.bundles.defaultStartLevel

So we thought...

At the console run the "sl" command to see what start-level the framework is set to and then run the "sl <bundle id>" command to see what start level your bundle is set to.  It seems like your bundles have a start-level that is higher than the current start-level of the framework.  There are two properties you should pay attention to.

osgi.bundles.defaultStartLevel - used to set the start-level of installed bundles that do not specify a particular start-level in the osgi.bundles list (defaults to 4).

osgi.startLevel - used to set the initial start-level of the framework (defaults to 6).

Yes, of course, we will double, double check that... I just got a queesy feeling that bundle default startlevel and framework startlevel was mixed up...

If you set osgi.bundles.defaultStartLevel > osgi.startLevel then your bundles will not be able to start because they will have a higher start-level than the current Framework start-level.  If this is not what is going on then please open a bug against PDE-UI.

Ok, thanks for the feedback...


equinox-dev mailing list

equinox-dev mailing list