[
https://issues.apache.org/jira/browse/SLING-6652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928392#comment-15928392
]
Dirk Rudolph commented on SLING-6652:
-------------------------------------
This is not what this is about. See I have a resource
{code}
/content/www/my/pages/apage
+ sling:resourceType='my/test/page'
+ ...
{code}
and want to export this resource once as metadata requested with
"model.metadata" and with "model.data" where each of the selectors represent
different models of the same resource. So I created
{code}
@Model(adaptables = Resource.class, resourceType='my/test/page')
@Exporter(..., selector="model.metadata")
class ModelA {
public String getProp1() { ... }
public String getProp2() { ... }
}
{code}
and
{code}
@Model(adaptables = Resource.class, resourceType='my/test/page')
@Exporter(..., selector="model.data")
class ModelB {
public String[] getAllProps() { ... }
}
{code}
This is a really simplified example where the actual code applies a lot of
*different* business logic within the different models.
> 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)
