[jira] Updated: (JCR-686) change some access-level modifiers to allow for better subclassing

[ http://issues.apache.org/jira/browse/JCR-686?page=all ] Stefan Guggisberg updated JCR-686: -- Summary: change some access-level modifiers to allow for better subclassing (was: loose some modifiers to allow better subclassing) change some

[jira] Commented: (JCR-686) change some access-level modifiers to allow for better subclassing

[ http://issues.apache.org/jira/browse/JCR-686?page=comments#action_12459881 ] Stefan Guggisberg commented on JCR-686: --- +1 for the patch change some access-level modifiers to allow for better subclassing

[jira] Commented: (JCR-686) change some access-level modifiers to allow for better subclassing

[ http://issues.apache.org/jira/browse/JCR-686?page=comments#action_12459884 ] Jukka Zitting commented on JCR-686: --- Looks OK. Do we need this already in 1.2.x? If yes, then I'd rather have it already in 1.2 instead of 1.2.1. If no, then I'd

[jira] Created: (JCR-687) UUID compareTo and hashCode

UUID compareTo and hashCode --- Key: JCR-687 URL: http://issues.apache.org/jira/browse/JCR-687 Project: Jackrabbit Issue Type: Bug Components: core Reporter: Thomas Mueller Priority:

[jira] Updated: (JCR-687) UUID compareTo and hashCode

[ http://issues.apache.org/jira/browse/JCR-687?page=all ] Thomas Mueller updated JCR-687: --- Attachment: uuid.txt Corrected compareTo and simplified hashCode implementations. UUID compareTo and hashCode --- Key:

[jira] Reopened: (JCR-685) Remove some synchronization on CachingNamespaceResolver

[ http://issues.apache.org/jira/browse/JCR-685?page=all ] Stefan Guggisberg reopened JCR-685: --- there are more synchronized methods that may lead to monitor contention Remove some synchronization on CachingNamespaceResolver

[jira] Commented: (JCR-685) Remove some synchronization on CachingNamespaceResolver

[ http://issues.apache.org/jira/browse/JCR-685?page=comments#action_12459931 ] Stefan Guggisberg commented on JCR-685: --- the following methods are synchronized on the CachingNamespaceResolver instance: QName retrieveName(String jcrName)

Re: Scalability concerns, Alfresco performance tests

Hi Andreas, sorry for my very delayed answer. In your answer on TheServerSide, you said that Scalability is mainly a matter of choosing and configuring the persistence layer correctly. Are there any scenario recommendations / best practises available? I'll check out the website again, but

[jira] Commented: (JCR-685) Remove some synchronization on CachingNamespaceResolver

[ http://issues.apache.org/jira/browse/JCR-685?page=comments#action_12459960 ] Stefan Guggisberg commented on JCR-685: --- How about this one? +1 Remove some synchronization on CachingNamespaceResolver

[jira] Resolved: (JCR-415) Enhance indexing of binary content

[ http://issues.apache.org/jira/browse/JCR-415?page=all ] Marcel Reutegger resolved JCR-415. -- Fix Version/s: 1.3 Resolution: Fixed In addition to the previously mentioned steps I also implemented the deferred text extraction as discussed with

Balancing Jackrabbit

Hi guys! I've 2 Tomcats behind a HW balancer. If I deploy one jackrabbit server all runs ok, but, when I try to deploy the second one I get the following message: javax.jcr.NamespaceException: failed to register namespace jlib - http://jlibrary.sourceforge.net: mapping already exists at

[jira] Commented: (JCR-685) Remove some synchronization on CachingNamespaceResolver

[ http://issues.apache.org/jira/browse/JCR-685?page=comments#action_12460069 ] Jukka Zitting commented on JCR-685: --- How about this one? -1 as it feels way too complicated, at least for 1.2. I also don't believe that replacing