Common Myths Around Sling Model
Fortunately I got a chance to talk to several people from AEM fraternity to understand their take about sling model and below are the summery of those discussions: Sling model is only back-end business logic provider to AEM components. Adaptable are just a way to get respective sling object reference. For example if you need slingRequest object in sling model then make your sling model adaptable to HttpSlingServletRequest. You can not get a value from sling model in a servlet or in any other class. When you need a reference of an OSGI service, you have only one way, that is @ OSGiService annotation. You can export only JSON data thru sling model exporter. You can not extend one sling model into another sling model. Sling model can to be created outside of the designated package in AEM. One Interface can not be a Sling Model, whenever you need to create a Sling Model you will have to write a pure POJO concrete implemented java class. You can only read properties of a node thru sling mod