sling-dev mailing list archives

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

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

Justin Edelson commented on SLING-6652:
---------------------------------------

This appears to be an XY problem. The actual thing you want is to register multiple model
classes with {{@Exporter}} annotations against the same resource type. This has very little
to do with *binding* a resourceType to a Model class. That binding is only needed for the
{{ModelFactory}} methods introduced in SLING-5992 (which as discussed in SLING-6655 is only
really relevant for loosly typed scripting languages). The fact that the these methods are
also used by the {{ExporterServlet}} is an implementation detail and one easily changed.

I'm attaching a patch which solves your problem without impacting the API semantics.



> 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)

Mime
View raw message