On 4/14/10 2:22 PM, Carsten Ziegeler wrote: > Carsten Ziegeler wrote >> Justin Edelson wrote > >>> I think this should just be a config option on >>> JcrResourceResolverFactoryImpl which bypasses the new code blocks >>> entirely. The only thing we need to watch out for here is that if you >>> enable non-default workspace observation, non-default workspace >>> resolution must be enabled, but this is reasonably simple to deal with. >> Ok, right - I think the configuration part is no problem. >> I'll try to add a switch to the code and see how it turns out >> > WDYT about using the already available > "resource.resolver.listener.workspaces" property from the factory? > > If this is set we enable the code, if this is not set, we disable the > code. Or is it more logical to have a separate boolean option? Maybe the other way around - replace this property with "resource.resolver.multiworkspace" which, if true, attaches listeners to all workspaces. There may be no need to listen to only a subset of workspaces.
Justin > > Regards > Carsten >
