Ticket #408 (closed Enhancement: wontfix)

Opened 8 years ago

Last modified 5 years ago

Core: do not register WebPublishingService as an OSGi service

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

Description (last modified by jri) (diff)

In fact the WebPublishing? service is designed as a private Core facility, not visible to plugins. So it should not be registered as an OSGi service.
This could speedup booting the server as well as the plugins must not wait for the WebPublishing? service to become available.

Change History

comment:1 Changed 8 years ago by jri

  • Status changed from new to accepted

comment:2 Changed 8 years ago by jri

  • Description modified (diff)

comment:3 Changed 8 years ago by jri

  • Milestone changed from Release 4.1 to Release 4.2

comment:4 Changed 7 years ago by dgf

  • Version 4.0.13 deleted
  • Milestone changed from Release 4.2 to Release 4.1.4

comment:5 Changed 7 years ago by jri

  • Milestone Release 4.1.4 deleted

comment:6 Changed 5 years ago by jri

  • Status changed from accepted to closed
  • Resolution set to wontfix

We go for the opposite approach now: The WebPublishing? service is now provided by a separate bundle. This supports better modularity and is more "OSGi like". See #834.

comment:7 Changed 5 years ago by jri

In b47f948610823e362692b72f78e010264f2a41f3:

Make WebPublishingService? internal to Core (#834).

The dm4-webpublishing module is dropped after all.

The WebPublishingService? is now a internal Core facility (as originally requested in #408).
It is deliberately not consumable as an OSGi service.

Plugin developers still import all standard event listeners from de.deepamehta.core.service.event.

See #834.
See #408.

Note: See TracTickets for help on using tickets.