[
https://issues.apache.org/jira/browse/SLING-8655?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16916523#comment-16916523
]
Stefan Seifert commented on SLING-8655:
---------------------------------------
yes, i'm also unsure if a PR like this does not fall too short once hitting
real life link resolving and externalization needs - multi tenancy aware etc.
it can be much more than just adding a hostname and a ".html" suffix.
we usually do it in the model code - calling a central piece of logic that does
the resolving, validation, externalization stuff. what is required in detail
may differ from use case to use case - internal, external links, asset links,
resources, with selectors etc.
> Add an Annotation to Sling Model to mark a property to be Externalized
> ----------------------------------------------------------------------
>
> Key: SLING-8655
> URL: https://issues.apache.org/jira/browse/SLING-8655
> Project: Sling
> Issue Type: New Feature
> Components: Sling Models
> Affects Versions: Sling Models API 1.3.8
> Reporter: Andreas Schaefer
> Assignee: Andreas Schaefer
> Priority: Major
> Fix For: Sling Models API 1.3.10
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> For Peregrine CMS we use Sling Models to obtain data in JSon format to be
> rendered on the client side. This means that the returned content is not
> externalized aka paths are not mapped to the external view.
> Sling Model should have an Annotation (@ExternalizedPath) that marks a
> property to be externalized when loaded.
> In order to be flexible the Externalized Path Injector should be pluggable so
> that customers can add their custom Externalized Path Providers if they
> choose to do so. By default there is a provider that uses the Resource
> Resolver's map() function.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
