Ticket #498 (closed Defect: fixed)

Opened 7 years ago

Last modified 7 years ago

DeepaMehta plugin detection fails sometimes

Reported by: jri Owned by: jri
Priority: Major Milestone: Release 4.2
Component: DeepaMehta Standard Distribution Version: 4.1
Keywords: Cc: dgf, Malte
Complexity: 2 Area:
Module: deepamehta-core

Description (last modified by jri) (diff)

Detection of DeepaMehta plugins (is a particular OSGi bundle a DM plugin?) is not accurate. This is the case when a plugin is not derived from PluginActivator? directly but only indirectly. This applies e.g. to web application plugins, which are derived from WebActivatorPlugin?.

Currently DM plugin detection is based on inspection of a bundle's package imports. A solution would be to inspect the actual class hierarchy of the bundle's activator class.

Change History

comment:1 Changed 7 years ago by jri

  • Status changed from new to accepted

comment:2 Changed 7 years ago by jri

  • Status changed from accepted to closed
  • Resolution set to fixed
  • Description modified (diff)
  • Summary changed from ALL_PLUGINS_ACTIVE event is fired more than once to DeepaMehta plugin detection fails sometimes

Core: fix DeepaMehta plugin detection (#498).

Plugin detection (is a particular OSGi bundle a DM plugin?) is based on inspecting the class hierarchy of the bundle's activator class.

Web application plugins (derived from WebActivatorPlugin?) are detected properly.

Close #498.

Changeset: cac81b32bd89513244aaf3c15fbba013fb7b6d5e

Note: See TracTickets for help on using tickets.