An implementation of Apache Isis' PublishingService and EventSerializer APIs, persisting a PublishedEvent record (through Isis' JDO Objectstore) for each changed published object or invoked published action, using a JSON format.
Java HTML Shell CSS
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.


Build Status

This module, intended for use with Apache Isis, provides an implementation of Isis' PublishingService API that persists published events using Isis' own (JDO) objectstore. The intention is that these are polled through some other process (for example using Apache Camel) so that external systems can be updated. To support this the persisted events have a simple state (QUEUED or PROCESSED) so that the updating process can keep track of which events are outstanding.

The module also contains an implementation of the related EventSerializer API. This is responsible for converting the published events into a string format for persistence; specifically JSON. The JSON representation used is that of the Restful Objects specification and includes the URL of the original publishing object such that it can be accessed using Isis' Restful Objects viewer if required.

Domain Model

A full description of Isis' Publishing Service API can be found on this page of the Isis website. However, the diagram below illustrates the main concepts:

The PublishedObject and PublishedAction annotations specify the event payload factory to use to create a representation of the event; if no factory is specified then a default factory is used.

The Isis runtime passes the event to the PublishingService so that it can be published. The PublishingService in turn delegates to the EventSerializer to create a representation of the provided event, along with various metadata about the event.

The diagram was generated by; see appendix at end of page for the DSL.


The following screenshots show an example app's usage of the module.

Installing the Fixture Data

Installing fixture data...

... returns a simplified customer object, with a name, an address, a collection of orders and also a list of published events as a contributed collection. The fixture setup results in one published event already:

Updating the Customer's Address (published action)

The customer's updateAddress action is a published action:

        publishing = Publishing.ENABLED,
        publishingPayloadFactory = PublishedCustomer.UpdateAddressEventPayloadFactory.class
public PublishedCustomer updateAddress(
        @ParameterLayout(named="Line 1") final String line1,
        @ParameterLayout(named="Line 2") @Parameter(optionality = Optionality.OPTIONAL) final String line2,
        @ParameterLayout(named="Town") final String town) {
    ReferencedAddress address = getAddress();
    if(address == null) {
        address = container.newTransientInstance(ReferencedAddress.class);
    return this;

When the action is invoked, a PublishedEvent is created by the framework, and persisted by the module:

The PublishedEvent holds the following details:

The serialized form field holds a JSON representation of the PublishedCustomer.UpdateAddressEventPayloadFactory class specified in the @PublishedAction annotation.

In addition, the ReferencedAddress entity is also a published object:

        publishing = Publishing.ENABLED // using the default payload factory
public class ReferencedAddress ... { ... }

This means that as well as raising and persisting the action invocation event, a separate event is raised and persisted for the change to the ReferencedAddress, the JSON representation of which includes a URL back to the changed address object:

Note that both the published events (for the action invocation on customer and the change of address) are associated by the same transaction Id (a GUID). This GUID can also be used to associate the event back to any persisted commands (as per the Isis Addons Command module and to any audit entries (as per the Isis Addons Audit module).

Updating the Customer's Name (published changed object)

Changes to the customer are also published:

        publishing = Publishing.ENABLED,
        publishingPayloadFactory = PublishedCustomer.ObjectChangedEventPayloadFactory.class
public class PublishedCustomer ... { ... }

In this case a custom payload factory is specified:

public static class ObjectChangedEventPayloadFactory implements PublishingPayloadFactoryForObject {
    public EventPayload payloadFor(final Object changedObject, final PublishingChangeKind publishingChangeKind) {
        return new PublishedCustomerPayload((PublishedCustomer) changedObject);
    public static class PublishedCustomerPayload extends EventPayloadForObjectChanged<PublishedCustomer> {

        public PublishedCustomerPayload(PublishedCustomer changed) { super(changed); }

        public String getAddressTown() {
            final ReferencedAddress address = getChanged().getAddress();
            return address != null? address.getTown(): null;
        public String getCustomerName() {
            return getChanged().getName();
        public SortedSet<ReferencedOrder> getOrders() {
            return getChanged().getOrders();

The custom payload exposes additional related information: the customer's name (a simple scalar), the customer's address' town (traversing a reference), and the orders of the customers (traversing a collection).

So, changing the customer's name:

... causes an event to persisted:

The additional information of the custom payload is captured in the serialized form of the event; in the screenshot below, see 'addressTown' property:

How to run the Demo App

The prerequisite software is:

  • Java JDK 8 (>= 1.9.0) or Java JDK 7 (<= 1.8.0) ** note that the compile source and target remains at JDK 7
  • maven 3 (3.2.x is recommended).

To build the demo app:

git clone
mvn clean install

To run the demo app:

mvn antrun:run -P self-host

Then log on using user: sven, password: pass

Relationship to Apache Isis Core

Isis Core 1.6.0 included the org.apache.isis.module:isis-module-publishing-jdo:1.6.0 and also org.apache.isis.module:isis-module-publishingeventserializer:1.6.0 Maven artifacts. This module is a direct copy of the code of those two modules, with the following changes:

  • package names have been altered from org.apache.isis to org.isisaddons.module.publishing
  • the persistent-unit (in the JDO manifest) has changed from isis-module-publishing to org-isisaddons-module-publishing-dom

Otherwise the functionality is identical; warts and all!

Isis 1.7.0 no longer ships with org.apache.isis.module:isis-module-publishing-jdo or org.apache.isis.module:isis-module-publishingeventserializer-ro; instead use this addon module.

How to configure/use

You can either use this module "out-of-the-box", or you can fork this repo and extend to your own requirements.


To use "out-of-the-box":

  • update your classpath by adding this dependency in your webapp project's pom.xml:
  • assuming you are using the provided RestfulObjectsSpecEventSerializer (that is, haven't written your own implementation of the EventSerializer API), then also update your classpath to add this dependency in your webapp project's pom.xml:

Check for later releases by searching Maven Central Repo.

  • if using AppManifest, then update its getModules() method:

    @Override public List> getModules() { return Arrays.asList( ... org.isisaddons.module.publishing.PublishingModule.class, ... ); }

  • otherwise, update your WEB-INF/

"Out-of-the-box" (-SNAPSHOT)

If you want to use the current -SNAPSHOT, then the steps are the same as above, except:

  • when updating the classpath, specify the appropriate -SNAPSHOT version:


  • add the repository definition to pick up the most recent snapshot (we use the Cloudbees continuous integration service). We suggest defining the repository in a <profile>:


Forking the repo

If instead you want to extend this module's functionality, then we recommend that you fork this repo. The repo is structured as follows:

  • pom.xml - parent pom
  • dom - the module implementation, depends on Isis applib
  • fixture - fixtures, holding a sample domain objects and fixture scripts; depends on dom
  • integtests - integration tests for the module; depends on fixture
  • webapp - demo webapp (see above screenshots); depends on dom and fixture

PublishedEvent serialized form

The PublishedEvent entity can either persist the serialized form of the event as a zipped byte array or as a CLOB. Which is used is determined by a configuration setting in

# whether to persist the event data as a "clob" or as a "zipped" byte[]

If not specified, then "zipped" is the default.

Setting the Base URL for the Restful Objects Event Serializer

The RestfulObjectsSpecEventSerializer serializes event payloads into a JSON string that contains URLs such that an external (subscribing) system can then access the publishing and related objects (using those URLs) by way of Isis' Restful Objects viewer.

For this to work correctly, the base url must be specified in, for example:


The default value if not specified is in fact http://localhost:8080/restful/ (for development/testing purposes only).

API & Implementation


The PublishingService API (in Isis' applib) is defined as:

public interface PublishingService {
    public void publish(EventMetadata metadata, EventPayload payload);
    void setEventSerializer(EventSerializer eventSerializer);

The EventMetadata is a concrete class with the fields:

public class EventMetadata {
    private final UUID transactionId;
    private final int sequence;
    private final String user;
    private final java.sql.Timestamp javaSqlTimestamp;
    private final String title;
    private final EventType eventType;
    private final String targetClass;
    private final String targetAction;
    private final Bookmark target;
    private final String actionIdentifier;


  • transactionId is a unique identifier (a GUID) of the transaction in which this event was raised.
  • sequence discriminates multiple events raised in a single transaction
  • user is the name of the user that invoked the action or otherwise caused the event to be raised
  • timestamp is the timestamp for the transaction
  • title is the title of the publishing object
  • eventType is an enum distinguishing action invocation or (for changed objects) object created/update/deleted,
  • targetClass holds the class of the publishing event, eg com.mycompany.myapp.Customer
  • targetAction is a user-friendly name for the action (applicable only for action invocation events)
  • target is a Bookmark of the target object, in other words a provides a mechanism to look up the publishing object, eg CUS:L_1234 to identify customer with id 1234. ("CUS" corresponds to the @ObjectType annotation/facet).
  • actionIdentifier is the formal/canonical action name (applicable only for action invocation events)

This module provides org.isisaddons.module.publishing.dom.PublishingService as an implementation of the API. The service is annotated with @DomainService so there is no requirement to register in


The EventSerializer API (in Isis' applib) is defined as:

public interface EventSerializer {
    public Object serialize(EventMetadata metadata, EventPayload payload);    

This module provides org.isisaddons.module.publishing.dom.eventserializer.RestfulObjectsSpecEventSerializer as an implementation of this API. Note that this service must be explicitly registered in and its Maven dependency on o.a.i.core:isis-core-viewer-restfulobjects-rendering must be added to the classpath (see above for details). This has been done to allow alternative implementations of the EventSerializer API to be configured instead if required.

Supporting Services

As well as the PublishingService and EventSerializer implementations, the module also provides a couple of other domain services:

  • PublishingServiceRepository provides the ability to search for persisted (PublishedEvent) events. None of its actions are visible in the user interface (they are all @Programmatic).

  • ThePublishingServiceMenu provides actions to search for PublishedEvents, underneath an 'Activity' menu on the secondary menu bar.

  • PublishingServiceContributions provides the publishedEvents contributed collection to the HasTransactionId interface. This will therefore display all published events that occurred in a given transaction.

  • RestfulObjectsSpecEventSerializer is an implementation of the EventSerializer API that serializes the event into a JSON representation based on that of the

In 1.7.0, it is necessary to explicitly register PublishingServiceContributions in, the rationale being that this service contributes functionality that appears in the user interface.

In 1.8.0 the above policy is reversed: the PublishingServiceMenu and PublishingServiceContributions services are both automatically registered, and both provide functionality that will appear in the user interface. If this is not required, then either use security permissions or write a vetoing subscriber on the event bus to hide this functionality, eg:

@DomainService(nature = NatureOfService.DOMAIN)
public class HideIsisAddonsPublishingFunctionality {

    @Programmatic @PostConstruct
    public void postConstruct() { eventBusService.register(this); }

    @Programmatic @PreDestroy
    public void preDestroy() { eventBusService.unregister(this); }

    @Programmatic @Subscribe
    public void on(final PublishingModule.ActionDomainEvent<?> event) { event.hide(); }

    private EventBusService eventBusService;

The default RestfulObjectsSpecEventSerializer is also automatically registered. If you want to use some other implementation of EventSerializer, then register in

Related Modules/Services

The Isis applib defines a number of closely related APIs.

The CommandContext defines the Command class which provides request-scoped information about an action invocation. Commands can be thought of as being the cause of an action; they are created "before the fact". The CommandService service is an optional service that acts as a Command factory and allows Commands to be persisted. CommandService's API introduces the concept of a transactionId; this is the same value as is passed to the PublishingService in the EventMetadata object.

The AuditingService3 service enables audit entries to be persisted for any change to any object. The command can be thought of as the "cause" of a change, the audit entries as the "effect".

If these services and also the PublishingService are all configured then the transactionId that is common to all (in the persisted command, audit entry and published event objects) enables seamless navigation between each. This is implemented through contributed actions/properties/collections; each of the persisted entities implements the HasTransactionId interface in Isis' applib, and it is this interface that each module has services that contribute to.

Implementations of these various services can be found on the Isis Add-ons website.

Finally, Dan Haywood's camel-isis-pubsubjdo project up on github shows how to poll and process the persisted PublishedEvent table using Apache Camel.

Change Log

  • 1.13.0 - Released against Isis 1.13.0
  • 1.12.0 - released against Isis 1.12.0
  • 1.11.0 - released against Isis 1.11.0
  • 1.10.0 - Released against Isis 1.10.0
  • 1.8.1 - Released against Isis 1.8.0; closes #1.
  • 1.8.0 - Released against Isis 1.8.0. Services are automatically registered; their UI can be suppressed using subscriptions.
  • 1.7.0 - Released against Isis 1.7.0.
  • 1.6.0 - re-released as part of isisaddons, with classes under package org.isisaddons.module.publishing

Legal Stuff


Copyright 2013~2016 Dan Haywood

Licensed under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License.  You may obtain a copy of the License at

Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.


There are no third-party dependencies.

Maven deploy notes

Only the dom module is deployed, and is done so using Sonatype's OSS support (see user guide).

Release to Sonatype's Snapshot Repo

To deploy a snapshot, use:

pushd dom
mvn clean deploy

The artifacts should be available in Sonatype's Snapshot Repo.

Release an Interim Build

If you have commit access to this project (or a fork of your own) then you can create interim releases using the script.

The idea is that this will - in a new branch - update the dom/pom.xml with a timestamped version (eg It then pushes the branch (and a tag) to the specified remote.

A CI server such as Jenkins can monitor the branches matching the wildcard origin/interim/* and create a build. These artifacts can then be published to a snapshot repository.

For example:

sh 1.14.0 origin


  • 1.14.0 is the base release
  • origin is the name of the remote to which you have permissions to write to.

Release to Maven Central

The script automates the release process. It performs the following:

  • performs a sanity check (mvn clean install -o) that everything builds ok
  • bumps the pom.xml to a specified release version, and tag
  • performs a double check (mvn clean install -o) that everything still builds ok
  • releases the code using mvn clean deploy
  • bumps the pom.xml to a specified release version

For example:

sh 1.13.0 \
              1.14.0-SNAPSHOT \
              "this is not really my passphrase"


  • $1 is the release version
  • $2 is the snapshot version
  • $3 is the email of the secret key (~/.gnupg/secring.gpg) to use for signing
  • $4 is the corresponding passphrase for that secret key.

Other ways of specifying the key and passphrase are available, see the pgp-maven-plugin's documentation).

If the script completes successfully, then push changes:

git push origin master
git push origin 1.13.0

If the script fails to complete, then identify the cause, perform a git reset --hard to start over and fix the issue before trying again. Note that in the dom's pom.xml the nexus-staging-maven-plugin has the autoReleaseAfterClose setting set to true (to automatically stage, close and the release the repo). You may want to set this to false if debugging an issue.

According to Sonatype's guide, it takes about 10 minutes to sync, but up to 2 hours to update search.

Appendix: DSL