Making a Post-transaction Filter
To make a post-transaction filter, create a Java class that extends the
abstract class
neo.xredsys.api.services.PostTransactionFilterService
.
This is a convenience class containing empty "do nothing"
implementations of the methods defined in the
neo.xredsys.api.PostTransactionFilter
interface:
doPostCreate(object)
-
which is executed immediately after a new object is saved.
doPostUpdate(object)
-
which is executed immediately after changes to an existing object are saved.
doStagedPostUpdate(object)
-
which is executed immediately after changes to an existing staged object are saved. For an explanation of staging, see Content Item Staging.
doPostDelete(object)
-
which is executed immediately after an existing object is deleted.
isEnabled()
-
which is called by the Content Engine to determine whether or not the filter is currently enabled.
Before a post-transaction filter can be used it must be:
-
Compiled
-
Added to the Content Engine's classpath
To compile a post-transaction filter you need the
Escenic
JAR file
engine-core-6.8.8-1.jar
in your classpath.