2014-01-29 Felix Meschberger <[email protected]> > Hi > The problem really is that the initial resolution does not have the > ResourceResolver available in the context yet, because only the > SlingMainServlet knows about it so far. > > Yepp
> So that leaves us with a two options: > > * keep the global filter, which at least sets an initial > HttpSerlvetRequest context > * implement a SlingRequestListener to extract the Resource Resolver from > the request attribute and add it to the context (instead of the Sling Level > Filter) > > Hmm, why can't the global filter ask for the request attribute? Carsten -- Carsten Ziegeler [email protected]
