[jira] Commented: (JCR-2433) NPE when copying nodes with Workspace.copy()

[ https://issues.apache.org/jira/browse/JCR-2433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12873146#action_12873146 ] Paul Jara commented on JCR-2433: Thanks Stefan. Yes I've Googled both of those error message

Jackrabbit Clustering

Hi , This is Suganthi from India. I am trying to configure Jackrabbit in clustered mode (Between Node A and Node B) in file system. I am using Tomcat server. I followed the instructions in http://wiki.apache.org/jackrabbit/Clustering . Both the repositories start successfully with no lock issue. Fo

[jira] Commented: (JCR-2639) consistencyCheck doesn't fix bad childnode

[ https://issues.apache.org/jira/browse/JCR-2639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12872985#action_12872985 ] Bart van der Schans commented on JCR-2639: -- There are two possible options: - remove

Re: [jr3] Security through obscurity

Hi, I'm sorry about the tone of my mails. I just want to avoid that we run into the trap of making Jackrabbit 3 much too complicated and complex for the sake of being "modular". I agree there shouldn't be many public implementation methods, but what I don't want to do is add additional "glue" cla

[jira] Commented: (JCR-2433) NPE when copying nodes with Workspace.copy()

[ https://issues.apache.org/jira/browse/JCR-2433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12872914#action_12872914 ] Stefan Guggisberg commented on JCR-2433: @paul: google is your friend... ;) FWIW,

Re: [jr3] Security through obscurity

hi, On Fri, May 28, 2010 at 10:31, Thomas Müller wrote: > Could those who suggest to get rid of the public implementation > methods please submit a patch for the Jackrabbit 3 prototype? We can > discuss from there. I don't think that's necessary. if there are specific concerns about the jackrabb

Re: [jr3] Security through obscurity

> well, i don't ;) i don't think that a proper oo design will > necessarily be "overly complex". Having everything convoluted just for the sake of avoiding public implementation methods is completely unrelated to proper OO design. It may be your understanding of proper OO design, but it's definite

Re: [jr3] Security through obscurity

On Fri, May 28, 2010 at 7:26 AM, KÖLL Claus wrote: > Hi, > > I must agree with Thomas. well, i don't ;) i don't think that a proper oo design will necessarily be "overly complex". cheers stefan > From my point of view public methods are no not so a problem. > I would prefere public Methods over