Hi Folks, Just pushed a new feature to master that I think will be of interest to many. Well some. One or two, perhaps? Whatever...
Anyway, the feature is a PublishingService that allows either action interactions or changed objects to be published, eg onto a JMS queue or similar. The programming model is a matter of adding @PublishedAction or @PublishedObject, and in registering a domain service that implements PublishingService. There's a default impl provided that just writes to stderr. There are also two serializers. The boring one just does a toString on the event payload. The more interesting one treats the payload as a (transient) domain object and renders it using the same representations as the Restful Objects viewer. Finally, the contents of the event payload can be customized. Under normal use all that is published (if using the RO event serializer) is the href of the objects. But the @PublishedAction and @PublishedObject annotations can specify a PayloadFactory that allows additional canonical information to be pushed out onto the wire. This won't be released for a month or two, I imagine, but - as I say - master has the changes. You can read more detail on the website [1] Cheers Dan [1] http://isis.apache.org/core/publishing-service.html
