> > I'm working on the documentation and struggled over the > > interface SlingScriptResolver. But I couldn't find any > > use of this interface. Maybe that's a relict from the time > > before Scripts are just Servlets? Today I think only the > > ServletResolver interface is used, or am I wrong? > > > Hi, > > yes, it's correct that the interface is currently not used > inside Sling. > And I guess there are only a few rare use cases for it. > > Basically you can use this service to script your OSGi service > or parts of it, by looking up the SlingScript from within > your service, > and calling it. > > You could do the same with searching for the script resource yourself > and adapting it to the ScriptHelper interface. > > It's more an utility method I think - therefore I think we have two > options: > a) keep the service > b) deprecate the service and create an utility method
Please excuse me if I don't get the whole picture. As far as I understand it, the SlingScriptResolver is intended to be implemented and also used by project specific code. If that is the case I strongly vote for b) to keep the API as clean as possible (microsling ;-)). Maybe that's a good time to document the scripting bundle. Can anyone point me to some information about the details of this bundle, I would then merge the information and put it on the website. best regards mike
