On 3/16/10 4:17 PM, Mike Müller wrote: > The case is what we discussed in [1]. There we came to the conclusion > to use a RequestEventListener. Otherwise we have to add a lifecycle > method like close or similar to the resource resolver or even to the > CredentialValidator where it definitly makes no sense. > So what's about using RequestEventListener? To my mind, two key things need to happen: 1) Felix's patch to FELIX-1962 should be applied. 2) Felix HttpService 2.0.6 is released
But I'm not sure we should be depending on a Felix-specific interface (ExtHttpService) in such a key piece of code. What really should be happening is to merge Felix HttpService's ExtHttpService interface into OSGi's HttpService interface (as HttpService version 2.0). Justin > An other possibility would be to insert not a plain JCR session but a > container which contains a JCR session into the request params. The > container then would check if there's access to the session and dispose > it after a while. But to be honest I don't like this idea that much. > > [1] http://markmail.org/message/bwgrbhwlsi5ekenn > > best regards > mike
