[SLING-6785] Add support for scoped lifecycle of sling models

• Type: New Feature
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: Models API 1.3.4, Sling Models Impl 1.4.0
• Component/s: Extensions
• Assignee: Justin Edelson
• Reporter: Christophe Jelger
• Created: 21/Apr/17 13:30
• Updated: 17/Apr/18 11:49
• Resolved: 27/Apr/17 13:38

Description

Similar to the scopes of JEE beans (http://docs.oracle.com/javaee/6/tutorial/doc/gjbbk.html), it would be nice to have the possibility to set a scope for sling models.

For example, a sling model instance could be reused for all the components within the same HTTP request, thus avoiding that multiple instances of the "same" model are created.

This could be an attribute of the @model annotation, for example something like:
@model(scope="request")

The request scope sounds straightforward for a sling model adapted from a request.

For models adapted from a resource, there are scenarios where the resource itself is not relevant once the model has been instantiated, so it would still be useful to be able to obtain the same model instance for different components and resources within the same HTTP request.

We could possibly have the same scopes than the JEE beans scope: request, session, and application.

Issue Links

• is related to: SLING-7586 [Sling Models] Memory Leak in cached adapters
• is related to: SLING-7095 Document Sling Models cache feature