> request.getServiceLocator().getService(ServletContext.class); and what about microsling? regards, philipp
On 12/12/07, Carsten Ziegeler <[EMAIL PROTECTED]> wrote: > Felix Meschberger wrote: > > Hi Betrand, > > > > Am Mittwoch, den 12.12.2007, 13:49 +0100 schrieb Bertrand Delacretaz: > >> Hi, > >> > >> Having access to ServletContext in scripts would be useful to allow > >> scripts to access java objects initialized by other servlets. > > > > This is definitely reasonable. Therefore the ServletContext is available > > as an OSGi Service in Sling. > > > >> If we agree, I'll add a suitable constant to SlingScriptEngine, and > >> change ScriptHelper and MicroslingScriptResolver accordingly. > > > > The SlingScriptEngine does not exist anymore. And I also think, that > > providing this through a constant is not a good thing. > > > > I could imagine, that we might provide the ServletContext through the > > SlingScriptHelper as getServletContext(). But I am not sure, whether is > > worth it if we can the servlet context through: > > > > request.getServiceLocator().getService(ServletContext.class); > > > > I would prefer this. > > > Me, too. > > Carsten > > -- > Carsten Ziegeler > [EMAIL PROTECTED] >
