You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Brendan Robert (JIRA)" <ji...@apache.org> on 2019/05/29 16:21:00 UTC

[jira] [Created] (SLING-8450) JcrPersist: Provide transparent persistence to Sling Models

Brendan Robert created SLING-8450:
-------------------------------------

             Summary: JcrPersist: Provide transparent persistence to Sling Models
                 Key: SLING-8450
                 URL: https://issues.apache.org/jira/browse/SLING-8450
             Project: Sling
          Issue Type: New Feature
          Components: API
            Reporter: Brendan Robert
         Attachments: SlingJCRPersist.zip

As a developer using sling, I would like my sling models to serve as a core of a MVC coding paradigm; however, it is not possible to do this without writing my own persistence logic to save my sling models back into resources for every project I do this.

I propose a new module to work in tandem with Sling Models, such that Sling Models serve as a mechanism to load data from JCR and the JcrPersist module provides an OSGi service to save changes to beans back to the JCR via a persist method.

There are some complex sling model features, such as @via, which will likely not be subject to this feature, and other cases such as transient variables that should not be persisted.  The persist service should provide the developer a sufficient set of features to decide how much or how little is persisted with it.  Like Sling Models, this should rely on annotations so that no additional external configurations are needed.

 

PS: Here's the implementation with ~90% unit test coverage.  See attached. :)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)