You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Marcel Reutegger (JIRA)" <ji...@apache.org> on 2008/03/17 14:51:24 UTC

[jira] Created: (JCR-1481) VersionHistory.removeVersion() does not throw ReferentialIntegrityException

VersionHistory.removeVersion() does not throw ReferentialIntegrityException
---------------------------------------------------------------------------

                 Key: JCR-1481
                 URL: https://issues.apache.org/jira/browse/JCR-1481
             Project: Jackrabbit
          Issue Type: Bug
          Components: jackrabbit-core, versioning
    Affects Versions: core 1.4.1, 1.4, core 1.4.2
            Reporter: Marcel Reutegger
            Priority: Minor


Inside an XATransaction immediately removing a version that was created by a checkin succeeds, even though it should fail because referential integrity is violated. The reason seems to be that the created version does not return any references.

In the end the transaction fails because referential integrity is checked again in the SharedItemStateManager, which is correct. But IMO removeVersion() should fail first.

Added test case: org.apache.jackrabbit.core.version.CheckinRemoveVersionTest

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (JCR-1481) VersionHistory.removeVersion() does not throw ReferentialIntegrityException

Posted by "Marcel Reutegger (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-1481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcel Reutegger resolved JCR-1481.
-----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5

Fixed in revision: 638430

> VersionHistory.removeVersion() does not throw ReferentialIntegrityException
> ---------------------------------------------------------------------------
>
>                 Key: JCR-1481
>                 URL: https://issues.apache.org/jira/browse/JCR-1481
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: jackrabbit-core, versioning
>    Affects Versions: 1.4, core 1.4.1, core 1.4.2
>            Reporter: Marcel Reutegger
>            Priority: Minor
>             Fix For: 1.5
>
>
> Inside an XATransaction immediately removing a version that was created by a checkin succeeds, even though it should fail because referential integrity is violated. The reason seems to be that the created version does not return any references.
> In the end the transaction fails because referential integrity is checked again in the SharedItemStateManager, which is correct. But IMO removeVersion() should fail first.
> Added test case: org.apache.jackrabbit.core.version.CheckinRemoveVersionTest

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (JCR-1481) VersionHistory.removeVersion() does not throw ReferentialIntegrityException

Posted by "Jukka Zitting (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/JCR-1481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jukka Zitting updated JCR-1481:
-------------------------------

    Fix Version/s:     (was: 1.5)
                   core 1.4.3

Merged to the 1.4 branch in revision 650335.

> VersionHistory.removeVersion() does not throw ReferentialIntegrityException
> ---------------------------------------------------------------------------
>
>                 Key: JCR-1481
>                 URL: https://issues.apache.org/jira/browse/JCR-1481
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: jackrabbit-core, versioning
>    Affects Versions: 1.4, core 1.4.1, core 1.4.2
>            Reporter: Marcel Reutegger
>            Priority: Minor
>             Fix For: core 1.4.3
>
>
> Inside an XATransaction immediately removing a version that was created by a checkin succeeds, even though it should fail because referential integrity is violated. The reason seems to be that the created version does not return any references.
> In the end the transaction fails because referential integrity is checked again in the SharedItemStateManager, which is correct. But IMO removeVersion() should fail first.
> Added test case: org.apache.jackrabbit.core.version.CheckinRemoveVersionTest

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.