Re: Modified externally exception due to eviction from shared ism cache

On Mon, May 17, 2010 at 9:46 PM, Marcel Reutegger wrote: > I just stumbled over the method > AbstractBundlePersistenceManager.load(PropertyId), which I think might > be related to this issue. > > what if the items states in the SISM indeed get cleared because the > local item states go into the ch

[jira] Commented: (JCR-2400) Import throws Exception when the repository contains sharable nodes

[ https://issues.apache.org/jira/browse/JCR-2400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12868516#action_12868516 ] Jervis Liu commented on JCR-2400: - Hi, I tried JackRabbit 2.1, still same exception. > Imp

Re: Build failed in Hudson: Jackrabbit-trunk » Jack rabbit Core #1145

Hi, On Mon, May 17, 2010 at 7:51 PM, Apache Hudson Server wrote: > [INFO] Too many unapproved licenses: 1 I fixed this in a subsequent commit. BR, Jukka Zitting

possibility of passing JCR TCK tests

Hi , I had an experience of pass of some tests in a package that i have not implemented .May be those are tests which have tests dependent on other packages that i have already implemented and tested successfully. So I just wanna know that ,if my JCR TCK passes a test ,that means I am done with th

Re: Modified externally exception due to eviction from shared ism cache

hi, I just stumbled over the method AbstractBundlePersistenceManager.load(PropertyId), which I think might be related to this issue. what if the items states in the SISM indeed get cleared because the local item states go into the change log? I guess this is more likely the bigger the change set

Build failed in Hudson: Jackrabbit-trunk #1145

See Changes: [Jukka Zitting] JCR-2631: Move backwards compatibility tests to trunk Set svn:ignore. Work in progress. [Jukka Zitting] JCR-2631: Move backwards compatibility tests to trunk Streamline the old repository cre

Build failed in Hudson: Jackrabb it-trunk » Jackrabbit Core #1145

See Changes: [Jukka Zitting] JCR-2631: Move backwards compatibility tests to trunk Set svn:ignore. Work in progress. [Jukka Zitting] JCR-2631: Move backwards compatibility tests to t

[jira] Resolved: (JCR-2631) Move backwards compatibility tests to trunk

[ https://issues.apache.org/jira/browse/JCR-2631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting resolved JCR-2631. Fix Version/s: 2.2.0 Resolution: Fixed The tests are now a part of jackrabbit-core. > Move ba

[jira] Updated: (JCR-2632) Concurrent Session.move() operations failure

[ https://issues.apache.org/jira/browse/JCR-2632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Guggisberg updated JCR-2632: --- Attachment: ConcurrentMoveTest.java test case for reproducing the issue > Concurrent Session.m

[jira] Created: (JCR-2632) Concurrent Session.move() operations failure

Concurrent Session.move() operations failure Key: JCR-2632 URL: https://issues.apache.org/jira/browse/JCR-2632 Project: Jackrabbit Content Repository Issue Type: Bug Components: jackrabb

[jira] Updated: (JCR-2630) UserAccessControlProvider handles users who dont have Jackrabbit managed Principals or User node incosistently.

[ https://issues.apache.org/jira/browse/JCR-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela updated JCR-2630: Fix Version/s: 2.2.0 > UserAccessControlProvider handles users who dont have Jackrabbit managed > Principals or User

[jira] Assigned: (JCR-2630) UserAccessControlProvider handles users who dont have Jackrabbit managed Principals or User node incosistently.

[ https://issues.apache.org/jira/browse/JCR-2630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela reassigned JCR-2630: --- Assignee: angela > UserAccessControlProvider handles users who dont have Jackrabbit managed > Principals or Us

Re: FYI: Moving session-related classes to o.a.j.core.session

Hi, On Mon, May 17, 2010 at 3:05 PM, Jukka Zitting wrote: > I'll prepare a patch and outline the steps by which I plan to address > the issues raised here. I'll commit the changes only when everyone is > happy with the approach. See JCR-890 for the proposed patch and a more detailed explanation

[jira] Updated: (JCR-890) concurrent read-only access to a session

[ https://issues.apache.org/jira/browse/JCR-890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting updated JCR-890: -- Attachment: session-class-move.patch > concurrent read-only access to a session >

[jira] Updated: (JCR-890) concurrent read-only access to a session

[ https://issues.apache.org/jira/browse/JCR-890?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jukka Zitting updated JCR-890: -- Attachment: session-class-move-norename.patch As a first step to implementing this, I'd like to make the f

[jira] Updated: (JCR-2625) spi2davex: reduce memory footprint of Node/PropertyInfoImpl

[ https://issues.apache.org/jira/browse/JCR-2625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Guggisberg updated JCR-2625: --- Status: Resolved (was: Patch Available) Fix Version/s: 2.2.0 Resolution: Fixe

[jira] Commented: (JCR-2625) spi2davex: reduce memory footprint of Node/PropertyInfoImpl

[ https://issues.apache.org/jira/browse/JCR-2625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12868224#action_12868224 ] Stefan Guggisberg commented on JCR-2625: > Looks good to me. Do the davex integration

Hudson build is back to normal : Jackrabbit-trunk #1143

See

Hudson build is back to normal : Jac krabbit-trunk » Jackrabbit Core #1143

See

[jira] Resolved: (JCR-2629) LoginModuleConfig should allow to specify principalProvider-name in addition to the class

[ https://issues.apache.org/jira/browse/JCR-2629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] angela resolved JCR-2629. - Resolution: Fixed > LoginModuleConfig should allow to specify principalProvider-name in addition > to the class >

Re: FYI: Moving session-related classes to o.a.j.core.session

Hi, On Mon, May 17, 2010 at 10:43 AM, Jukka Zitting wrote: > Unless there's a need to wait, I'm planning to commit the changes in > the afternoon today. This obviously needs more time than I anticipated. I'm sorry about the rush. I'll prepare a patch and outline the steps by which I plan to add

[jira] Commented: (JCR-2625) spi2davex: reduce memory footprint of Node/PropertyInfoImpl

[ https://issues.apache.org/jira/browse/JCR-2625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12868210#action_12868210 ] Michael Dürig commented on JCR-2625: Looks good to me. Do the davex integration tests sti

Re: Build failed in Hudson: Jackrabbit-trunk » Jack rabbit Core #1142

Hi, On Fri, May 14, 2010 at 9:12 PM, Jukka Zitting wrote: > On Fri, May 14, 2010 at 7:17 PM, Apache Hudson Server > wrote: >> Failure executing javac, but could not parse the error: >> An exception has occurred in the compiler (1.5.0_14). Please file a bug at >> the >> Java Developer Connection

Re: FYI: Moving session-related classes to o.a.j.core.session

Hi, As far as I understand, you want to move the classes so we can add checkstyle / PMD constraints, and more easily ensure every method call from an external class is synchronized. I think that's fine. Having the 'proxy' classes sounds like a solution for the backward compatibility concerns (not

Re: FYI: Moving session-related classes to o.a.j.core.session

Hi, On Mon, May 17, 2010 at 11:34 AM, Thomas Müller wrote: >> These unrelated classes are mostly things like RepositoryImpl, >> TransientRepository, RepositoryCopier, etc. to which many external >> codebases are linking, so we can't move them. > > SessionImpl is used in my applications as well.

Re: FYI: Moving session-related classes to o.a.j.core.session

On Mon, May 17, 2010 at 10:16 AM, Jukka Zitting wrote: > These unrelated classes are mostly things like RepositoryImpl, > TransientRepository, RepositoryCopier, etc. to which many external > codebases are linking, so we can't move them. All class inside core has possible reference for user code ba

Re: FYI: Moving session-related classes to o.a.j.core.session

Hi, > These unrelated classes are mostly things like RepositoryImpl, > TransientRepository, RepositoryCopier, etc. to which many external > codebases are linking, so we can't move them. SessionImpl is used in my applications as well. > RepositoryImpl, > TransientRepository I don't think those s

Re: FYI: Moving session-related classes to o.a.j.core.session

Stefan Guggisberg wrote: i share tomas's concerns. so do i... in addition i have quite some changes pending (JCR-2573, JCR-2629), which are not yet ready for commit. UserPerWorkspaceSecurityManager (>security), DefaultSecurityManager (>security), that doesn't work without major changes. th

Re: FYI: Moving session-related classes to o.a.j.core.session

Hi, On Mon, May 17, 2010 at 11:00 AM, Thomas Müller wrote: > - If you move classes to other packages, you will have to make many > method public. My ultimate goal is to track down all these cases and refactor them away so we can better control all the code paths to and from a single session. By

Re: FYI: Moving session-related classes to o.a.j.core.session

On Mon, May 17, 2010 at 11:00 AM, Thomas Müller wrote: > Hi, > > I'm not sure if this will help more than it will complicate things. > Disadvantages: > > - Isn't almost every class at in o.a.j.core at least somewhat session related? > > - If you move classes to other packages, you will have to mak

Re: FYI: Moving session-related classes to o.a.j.core.session

Hi, I'm not sure if this will help more than it will complicate things. Disadvantages: - Isn't almost every class at in o.a.j.core at least somewhat session related? - If you move classes to other packages, you will have to make many method public. Instead of moving session related classes to a

FYI: Moving session-related classes to o.a.j.core.session

Hi, As a part of my work on JCR-890, I'm planning to move most of the session-related classes from o.a.j.core to a new o.a.j.core.session package. This will make it easier to review and control related dependencies and code paths, and to ultimately guard them against access from concurrent threads

[jira] Commented: (JCR-2625) spi2davex: reduce memory footprint of Node/PropertyInfoImpl

[ https://issues.apache.org/jira/browse/JCR-2625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12868126#action_12868126 ] Stefan Guggisberg commented on JCR-2625: > I was wondering if it makes sense to build

[jira] Commented: (JCR-2396) File Journal workaround for misbehaving NFS implementations

[ https://issues.apache.org/jira/browse/JCR-2396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12868123#action_12868123 ] Thomas Mueller commented on JCR-2396: - > Was this patch applied to the 2.x line? No, th

Re: problem with workspace when testing with JCR TCK

hi, these are probably the read-only tests that require content. please have a look at the class TestContentLoader in jackrabbit-core. it adds test data to a jackrabbit repository to run the jcr tests. preparing your repository with similar data should do the trick. regards marcel On Thu, May

Re: AW: jackrabbit on hadoop

hi, the module had a snapshot dependency to jackrabbit-core. I fixed that and the build should now work. please note that you have to manually deploy the hbase and hadoop-core dependencies and don't forget to patch hbase! see also the readme file [0]. see attached repository.xml and workspace.xml

[jira] Commented: (JCR-2625) spi2davex: reduce memory footprint of Node/PropertyInfoImpl

[ https://issues.apache.org/jira/browse/JCR-2625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12868113#action_12868113 ] Marcel Reutegger commented on JCR-2625: --- I was wondering if it makes sense to build the