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 from the JcrResourceResolverFactoryImpl
(bindResourceProdiver method)
or.. because of local modification I am running an out of date
JcrResourceResolverFactoryImpl .... oops .... wipes egg off
face.....that will teach me to make mods to implementation code :)
Having fixed this problem in my code base, I re-factored my
modifications to minimize the patch to the sling code base, resulting
in some extension points to JcrResourceResolver2. This represents no
change in functionality in Sling but does allow those extending to do
it in a sensible way. See [1], WDYT? Ok for inclusion ?
Ian
1 https://issues.apache.org/jira/browse/SLING-1129
