You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Konrad Windszus (JIRA)" <ji...@apache.org> on 2016/05/20 15:07:13 UTC

[jira] [Issue Comment Deleted] (SLING-5739) [Sling Models] Allow for extensible @Via providers

     [ https://issues.apache.org/jira/browse/SLING-5739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Konrad Windszus updated SLING-5739:
-----------------------------------
    Comment: was deleted

(was: This is different than the other Via then. For example when using Via on the ValueMapInjector, the Via is applied before it comes to the injector. Here it is the other way round.)

> [Sling Models] Allow for extensible @Via providers
> --------------------------------------------------
>
>                 Key: SLING-5739
>                 URL: https://issues.apache.org/jira/browse/SLING-5739
>             Project: Sling
>          Issue Type: New Feature
>          Components: Extensions
>            Reporter: Justin Edelson
>
> Currently, @Via support in Sling Models is limited to JavaBean properties. It would be useful to be able to extend this and allow for downstream projects to add new @Via providers.
> Proposing to support this by extending the @Via annotation
> {code}
> @Via(value = "jcr:content", type = ChildResource.class)
> {code}
> The default type is BeanProperty (the current behavior).
> New providers can be added by implementing a ViaProvider SPI and provide a marker class for use in the annotation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)