You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Jukka Zitting (JIRA)" <ji...@apache.org> on 2008/04/22 02:47:22 UTC
[jira] Updated: (JCR-1481) VersionHistory.removeVersion() does not
throw ReferentialIntegrityException
[ 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.