You are viewing a plain text version of this content. The canonical link for it is here.
Posted to slide-user@jakarta.apache.org by Kiran Patchigolla <Ki...@Hyperion.com> on 2004/08/28 02:20:26 UTC

Copy Macro Issue

I am facing issues with using copy macro for copying versioned objects. Here
is a sample scenario:

 

Original object:

Name: XYZ.doc

Number of Versions: 3 v1, v2 and v3

Checked-in property value: v3

 

1. Copy the object using the copy macro. The Destination copied object has
the following properties:

            Name: CopiedXYZ.doc

            Checked-in property value: v3

 

The problem is both the original and the copied object are referring to the
same history node v3. 

 

2. Add a new version v4 to the original object:

Name: XYZ.doc

Number of Versions: 4 v1, v2, v3 and v4

Checked-in property value: v4

 

3. At this point the new (copied) object still has the checked-in property
as v3.

            Name: CopiedXYZ.doc

            Checked-in property value: v3

4. Now try adding a new version to the new (copied) object. This will throw
a precondition violation say that checkouts with descendants is not allowed.
Since I am trying to check out v3, when there is already a successor for v3,
which is v4 created by the original object.

 

This seems a pretty basic flaw in the copy macro. Ideally it should be
creating new history nodes for the new (copied) object. Is this a known
issue? Does the copy macro does support copying versioned objects? If it
does, this problem should be fixed. If it does not, it should not be copying
version related properties.

 

Thanks

Kiran



************************************************************************

If you have received this e-mail in error, please delete it and notify the sender as soon as possible. The contents of this e-mail may be confidential and the unauthorized use, copying, or dissemination of it and any attachments to it, is prohibited. 

Internet communications are not secure and Hyperion does not, therefore, accept legal responsibility for the contents of this message nor for any damage caused by viruses.  The views expressed here do not necessarily represent those of Hyperion.

For more information about Hyperion, please visit our Web site at www.hyperion.com