This issue concerns the functionality that implements the mechanism of content publication. When content objects are created with their status set to "scheduledForPublication" a mechanism should be implemented by the content application that periodically examines the content objects and appropriately changes their status to "puplished".

Currently this is implemented as spring bean that utilizes the quartz scheduler. The implementation will change and a seam asynchronous method will be provided. The content application that utilizes the "betacms-portal-commons" module should be responsible to call the asynchronous method in order to initialize the puplication scheduling process. The implemented method will also generated a seam event before saving and after saving each published object to allow the interested clients to perform some pre and post-publication actions.

Delegating the scheduling of content publication to the content application instead of a central repository mechanism is quite effective assuming that only one content application runs. In the case that multiple applications use the content repository there should be some coordination of which application will do the scheduling.

At a later version we will move the scheduling of content publication at the central ESB module that is provided together with the content repository engine.