Ticket #834 (closed Enhancement: fixed)

Opened 9 years ago

Last modified 9 years ago

Separate WebPublishingService from Core

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


Change History

comment:1 Changed 9 years ago by jri

  • Status changed from new to accepted

comment:2 Changed 9 years ago by Jörg Richter <jri@…>

In e849dfd62231358df05274ac2ea81d25616f88a9/deepamehta:

Separate WebPublishingService? from Core (#834).

New module:



7 listeners are moved from de.deepamehta.core.service.event to de.deepamehta.webpublishing.listeners:


See #834.

comment:3 Changed 9 years ago by jri

In 69b303cf57fe962ae658f3057aef81bc7920037e:

Revise web publishing wording (#834).

"Static Resources" comprise "Web Resources" and "File System Resources".

Web Resources (as found in a bundle's /web directory) are no longer referred to as Static Resources.

"Static Resources" is only used when

  • referring to Bundle resources which are not web resources
  • meaning the generic sense as mentioned above

See #834.

comment:4 Changed 9 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.

comment:5 Changed 9 years ago by jri

  • Status changed from accepted to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.