[SLING-3886] Sling Models: support adapters for models different from the implementation class

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: Sling Models API 1.1.0, Sling Models Implementation 1.1.0
• Component/s: Extensions
• Labels: models
• Assignee: Justin Edelson
• Reporter: Stefan Seifert
• Created: 27/Aug/14 08:43
• Updated: 02/Sep/14 19:04
• Resolved: 02/Sep/14 19:04

Description

currently, as adapter (adaption target) only the implementation class itself that is annotated with the @Model annotation is supported (which can be either an interface or a class).

if the model is not just a simple model but a class with more complex business logic the following scenario is required:

• a "service" interface is defined
• this service interface ist not directly mapped to injected values, but provides higher-level method
• an implementation class with @Model annotation is implemented which gets the required values injectd internally, but implements the interface for outside access

this is currently not possible with sling models.

the attached patch extends the following features:

• extends the @Model annotation with an optional "adapters" attribute
• if defined, only the listed adapters are registered for the adapter factory, not the implementation class itself (unless it is listed the "adapters" attribute as well)
• in the adapters attribute only the implementation class itself or interfaces that it implements or superclasses can be defined
• with this the scenario above is perfectly possible
• unit tests included which simulate the bundle add/remove usecases which is required to do the indirect implementation class mapping