|Version status: 0.0.3 beta|
Depends on tapestry-jpa and tapestry-ckeditor modules
Here's how it looks like:
|When user is unauthenticated||Content is being edited|
|When authenticated with the configured editor role|
An example page template:
The module uses HttpServletRequest.getRemoteUser() and HttpServletRequest.isUserInRole(String role) for permission checks. Tapestry-security provides a built-in wrapper for handling these operations, but you don't have to use tapestry-security with this module, instead you could easily provide your own advisor for HttpservletRequest if you like. The module also keeps track of versions, however at the moment, there's no user interface for reverting to previous versions. Currently, JPA is the only persistence strategy implemented. For configuring JPA, see "Integrating with JPA", of Tapestry 5 documentation.