[ https://issues.apache.org/jira/browse/SLING-6652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dirk Rudolph updated SLING-6652: -------------------------------- Description: 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. This mechanism is used in the ExportServlet to get the Object form either {{SlingHttpServletRequest}} or {{Resource}}. 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. was: 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. Summary: Allow multiple Exporter annotated models being used with the same resourceType binding (was: Allow multiple adapters for Models with resourceType binding) Change the title better express, what this ticket is about. > Allow multiple Exporter annotated models being used with the same > 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. > This mechanism is used in the ExportServlet to get the Object form either > {{SlingHttpServletRequest}} or {{Resource}}. > 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)