[SLING-6966] Sling Models Jackson Exporter always uses default Resource serialization for a model class which extends AbstractResource or implements the Resource interface

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Models Jackson Exporter 1.0.6
• Fix Version/s: Models Jackson Exporter 1.0.8
• Component/s: Extensions
• Assignee: Justin Edelson
• Reporter: Justin Edelson
• Created: 19/Jun/17 15:14
• Updated: 28/Aug/17 13:10
• Resolved: 19/Jun/17 15:28

Description

If there is a model class which looks like this:

@Model(adaptable = SlingHttpServletRequest.class, resourceType = "something")
@Exporter(name = "jackson", extensions = "json")
public class Foo extends AbstractResource {

....

}

Then attempts to export this resource will always use the default Resource serialization and not use the "bean" serialization technique used by Jackson. This is because Jackson will first find the ResourceSerializer based on the Resource interface before constructing a BeanSerializer. The serializer lookup logic should be customized to skip any class with the @Model annotation.