sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dirk Rudolph (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SLING-6652) Allow multiple adapters for Models with resourceType binding
Date Fri, 17 Mar 2017 12:32:42 GMT

    [ https://issues.apache.org/jira/browse/SLING-6652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15929890#comment-15929890
] 

Dirk Rudolph commented on SLING-6652:
-------------------------------------

Its indeed explained in https://issues.apache.org/jira/browse/SLING-3886?focusedCommentId=14112711&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14112711.
The only concern I have is that we implicitly expect the {{adapterType}}s being sorted in
a certain way, which - I'm not sure - might not be clear to those developers using it. 

Having said that, [~sseifert@pro-vision.de] didn't had a problem making {{implType}} always
part of the {{adapterType}}s. So +1 for that, wdyt?



> Allow multiple adapters for Models with resourceType binding
> ------------------------------------------------------------
>
>                 Key: SLING-6652
>                 URL: https://issues.apache.org/jira/browse/SLING-6652
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: Sling Models Impl 1.3.0
>            Reporter: Dirk Rudolph
>         Attachments: SLING-6652.diff
>
>
> According to http://svn.apache.org/viewvc/sling/trunk/bundles/extensions/models/impl/src/main/java/org/apache/sling/models/impl/AdapterImplementations.java?view=markup#l59
the AdapterImplementations support only mapping resourceType to Adapter 1:1. I would like
to propose extending that to support 1:n binding between resourceType and adapter classes.
> My use case: 
> Lets assume I want to combine my models with the exporter framework to export 2 representations
of a single resource:
> * metadata
> * data
> To do so I would create 2 models, each bound to the same resourceType but annotated to
be exported for different selectors. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message