On 25 Sep 2009, at 12:49, Ian Boston wrote:
Yes, everything is possible :)
Maybe - for whatever reason - the sling servlet resolver is not
registered as an event handler anymore (therefore it should be
registered as EventHandler and have the property event.topics).
Or the event is not fired f
On 25 Sep 2009, at 12:41, Carsten Ziegeler wrote:
Ian Boston wrote
but I never see the handleEvent method invoked to reset the cache, I
guess that I have done something to the event registration process
surrounding the SlingServletResolver, but doing event registrations
(or
breaking the ev
Ian Boston wrote
>
> but I never see the handleEvent method invoked to reset the cache, I
> guess that I have done something to the event registration process
> surrounding the SlingServletResolver, but doing event registrations (or
> breaking the event flow) somewhere else ? Is that possible ?
>
On 25 Sep 2009, at 11:51, Ian Boston wrote:
On 25 Sep 2009, at 11:32, Ian Boston wrote:
On 25 Sep 2009, at 11:09, Carsten Ziegeler wrote:
Ian Boston wrote:
Has anyone noticed problems reloading a servlet bundle ?
After a reload of a bundle containing a servlet I find that the
original
On 25 Sep 2009, at 11:32, Ian Boston wrote:
On 25 Sep 2009, at 11:09, Carsten Ziegeler wrote:
Ian Boston wrote:
Has anyone noticed problems reloading a servlet bundle ?
After a reload of a bundle containing a servlet I find that the
original
servlet is still used, verified by logging "t
On 25 Sep 2009, at 11:09, Carsten Ziegeler wrote:
Ian Boston wrote:
Has anyone noticed problems reloading a servlet bundle ?
After a reload of a bundle containing a servlet I find that the
original
servlet is still used, verified by logging "this".
I know the old servlet was unloaded by O
Ian Boston wrote:
> Has anyone noticed problems reloading a servlet bundle ?
>
> After a reload of a bundle containing a servlet I find that the original
> servlet is still used, verified by logging "this".
>
> I know the old servlet was unloaded by OSGi since its references become
> null after t
On 25 Sep 2009, at 11:03, Vidar Ramdal wrote:
On Fri, Sep 25, 2009 at 11:55 AM, Ian Boston wrote:
Has anyone noticed problems reloading a servlet bundle ?
After a reload of a bundle containing a servlet I find that the
original
servlet is still used, verified by logging "this".
Using JC
On Fri, Sep 25, 2009 at 11:55 AM, Ian Boston wrote:
> Has anyone noticed problems reloading a servlet bundle ?
>
> After a reload of a bundle containing a servlet I find that the original
> servlet is still used, verified by logging "this".
Using JCRInstall, by any chance?
https://issues.apache.
Has anyone noticed problems reloading a servlet bundle ?
After a reload of a bundle containing a servlet I find that the
original servlet is still used, verified by logging "this".
I know the old servlet was unloaded by OSGi since its references
become null after the reload. It looks like t
10 matches
Mail list logo
