Did Alfresco 1.4 include any JCR improvements?

[lfuller]

We are currently evaluating various JSR170 content repositories for a large publishing company that has stated they have a need to develop a highly scalable portlet application built upon JSR 170 api.  Of particular concern are search related scalability issues due to xPath's poor performance.  In previous threads I heard a mention that in the future Alfresco's implementation of the JCR might be reworked to leverage Lucene for better performance.
Has this happened?
As it stands now it looks a lot like CRX may end up being the preferred option

[paulhh]

Hi Lennard

We have literally just found an improvement that can be made to our XPath implementation - so knowing what we're trying to beat would help us see whether we can meet the requirements.  We do plan to overhaul the query implementations, but this will take a few months and come after the next release (early next year).

As this is a commercial opportunity, it may be best to take it offline from the public forums - sales@alfresco.com will get routed to someone who will help.

Cheers
Paul.

[paulhh]

Also, when we were benchmarking Alfresco, we did some ad hoc comparative tests with JackRabbit - and our XPath was noticeably faster.  The impression people have given us is that CRX is 95% JackRabbit.

Cheers
Paul.