[
https://issues.apache.org/jira/browse/SLING-6652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15929998#comment-15929998
]
ASF GitHub Bot commented on SLING-6652:
---------------------------------------
GitHub user Buuhuu opened a pull request:
https://github.com/apache/sling/pull/207
SLING-6652
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Buuhuu/sling feature/SLING-6652-+-SLING-6658
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/sling/pull/207.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #207
----
commit ee46f4884373c434c614ce025b40f0a826045a3c
Author: Dirk Rudolph <[email protected]>
Date: 2017-03-17T07:47:45Z
SLING-6652:
- applied justin’s patch
commit ec8564eaf6cda06e025607f885fe48617b28d8b6
Author: Dirk Rudolph <[email protected]>
Date: 2017-03-17T07:51:30Z
SLING-6658:
- always reigster the model with its implType, even not specified as
adapter explicitly
commit 53f22ad86012b9f83f3b4163b12853e54b3b4680
Author: Dirk Rudolph <[email protected]>
Date: 2017-03-17T13:18:17Z
Merge remote-tracking branch 'origin/feature/SLING-6658' into
feature/SLING-6652-+-SLING-6658
commit 7d2b8250881804c77b6eb822126a75ab37b9e77f
Author: Dirk Rudolph <[email protected]>
Date: 2017-03-17T13:31:38Z
SLING-6652:
- moved logic collection Exporter annotations out of the nested for loops.
commit 29a1c8d4cc60fe205219e35f64f5ab03f6356fd2
Author: Dirk Rudolph <[email protected]>
Date: 2017-03-17T13:32:31Z
SLING-6652:
- instantiate accessor using concret implType instead of implicitly
assuming the first of the adapterTypes should be taken
commit e32d4d617f9d5f1443d5969bd18904dc4fae1984
Author: Dirk Rudolph <[email protected]>
Date: 2017-03-17T13:49:05Z
Merge remote-tracking branch 'origin/trunk2' into
feature/SLING-6652-+-SLING-6658
# Conflicts:
#
bundles/extensions/models/integration-tests/src/main/java/org/apache/sling/models/it/ImplementsExtendsTest.java
----
> 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)
