[
https://issues.apache.org/jira/browse/SLING-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Feike Visser updated SLING-6504:
--------------------------------
Description:
The current implementation of the Use-api accept classes that are adaptable
from Request or Resource.
This issue is to make this mechanism more flexible, to be able to adapt from
different objects.
Proposal:
{code}
data-sly-use="com.example.Class from resourceResolver"
{code}
{code}
data-sly-use="com.example.Class from yourCustomObject"
{code}
was:
The current implementation of the Use-api accept classes that are adaptable
from Request or Resource. But in many cases it would also be great if they can
be adaptable from ResourceResolver.
Now you need to write a small wrapper to get the resourceResolver and adapt to
the class.
Summary: Use-api to support more flexible way to adapt (was: Use-api
also adaptable from ResourceResolver)
> Use-api to support more flexible way to adapt
> ---------------------------------------------
>
> Key: SLING-6504
> URL: https://issues.apache.org/jira/browse/SLING-6504
> Project: Sling
> Issue Type: Improvement
> Components: Scripting
> Reporter: Feike Visser
> Labels: Sightly
>
> The current implementation of the Use-api accept classes that are adaptable
> from Request or Resource.
> This issue is to make this mechanism more flexible, to be able to adapt from
> different objects.
> Proposal:
> {code}
> data-sly-use="com.example.Class from resourceResolver"
> {code}
> {code}
> data-sly-use="com.example.Class from yourCustomObject"
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
