Justin Edelson wrote
> While looking at the threads web console plugin (my best friend as of
> late), I noticed that the
> org.apache.sling.event.impl.jobs.jcr.LockManager component was taking
> a long time to activate.
>
> Looking at the code, I see that a JCR SQL2 query is used on line 314:
> final Query q = qm.createQuery("select * from [nt:base]
> where [" + JCRHelper.NODE_PROPERTY_LOCK_OWNER + "] = '" + searchString
> + "'",
> Query.JCR_SQL2);
>
> Is there any reason why this needs to be a SQL2 query? It doesn't
> appear that way.
>
> This isn't a part of the codebase which I've done a lot of work in, so
> I didn't want to change it to XPath without getting some feedback.
>
No, there is no real reason behind it - except that I wanted to avoid
deprecated features - but if the new stuff is slow compared to the
deprecated versions (which is really odd) than we should simpyl switch back.
Regards
Carsten
--
Carsten Ziegeler
[email protected]
