[ https://issues.apache.org/jira/browse/SLING-6652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928670#comment-15928670 ]
Justin Edelson commented on SLING-6652: --------------------------------------- Looking at the Pull Request and reading the original description, I'm a little confused about the problem you are trying to solve. If this is really about having different model classes respond to different selector/extension combinations, then no API changes should be required (except maybe a new annotation attribute but even that is debatable). If instead you actually want to define new APIs, the use case for those APIs should be described. Right now, the description of this issue *only* talks about Exporters. > 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 > > 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)