sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Edelson (JIRA)" <>
Subject [jira] [Updated] (SLING-6652) Allow multiple adapters for Models with resourceType binding
Date Fri, 17 Mar 2017 00:54:42 GMT


Justin Edelson updated SLING-6652:
    Attachment: SLING-6652.diff

The only problem with this patch is that there is still a warning output:

Skipped registering class for resourceType
sling/exp/doubled under adaptable interface because
of existing mapping to class

To me, this is not a problem, but if is troublesome, we can add an attribute to the {{@Model}}
annotation which causes the binding to be skipped.

> Allow multiple adapters for Models with resourceType binding
> ------------------------------------------------------------
>                 Key: SLING-6652
>                 URL:
>             Project: Sling
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: Sling Models Impl 1.3.0
>            Reporter: Dirk Rudolph
>         Attachments: SLING-6652.diff
> According to
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

View raw message