Hi Justin, another useful feature just came to my mind (in fact we are using it in our own annotation framework) which is composition. Would it be much effort to allow injecting one model into another? We do have the following usecase for that (although this is CQ, I guess there is a similar usecase in Sling only):
You have a model for an image with title, alternative text. You have a model for multiline text fields and alignment. There exist resourceTypes for each of the models as well as a composite resourceType multilineImage. For the composite resourceType I would like to reuse the existing models, but I cannot split up the view (i.e. the JSPs and work with sling:include), because the html is somehow intertwined. Therefore I would define another composite model exposing the models for both image and multiline and use that composite model in my JSP. It would be great if for the injection of other models it would be possible to switch the current resource as well (i.e. descent into subnode image). That do you think about that? Thanks in advance, Konrad Am 19.12.2013 um 18:07 schrieb Justin Edelson <[email protected]>: > Hi, > I've published a page to the wiki about a concept I've been working on > to consolidate the various appproaches I have seen in the wild to > model object creation. I'm calling this YAMF for now, although ideally > we'll just call it Sling Models :) > > Without repeating the whole contents of the wiki page, at a high > level, this is a purely annotation driven approach supporting both > classes and interfaces. Your model class simply needs to declare from > which other classes it can be adapted: > > @Model(adaptables=Resource.class) > > And then annotate the fields (for classes) and methods (for > interfaces) which need injection: > > @Inject > private String propertyName; > > You can inject properties, OSGi services, request attributes, and > entries from SlingBindings. > > New injector types can be created through an SPI. > > Additional annotations are supported for special cases: > > @Optional - mark a field/method as optional. > @Filter - provide a filter (i.e. for OSGi services) > @Named - specify a name (other than the default field/method name) to > use for the inejction lookup. > > More detail can be found here: > https://cwiki.apache.org/confluence/display/SLING/YAMF+-+Yet+Another+Model+Factory > > The working code is up in my whiteboard: > https://svn.apache.org/repos/asf/sling/whiteboard/justin/yamf/ > > Look forward to your feedback. > > Regards, > Justin
