jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sreekanth S Nair (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (OCM-42) OCM Versioning is not working as expected
Date Mon, 29 Mar 2010 05:43:27 GMT

     [ https://issues.apache.org/jira/browse/OCM-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Sreekanth S Nair resolved OCM-42.

    Resolution: Fixed

> OCM Versioning is not working as expected
> -----------------------------------------
>                 Key: OCM-42
>                 URL: https://issues.apache.org/jira/browse/OCM-42
>             Project: Jackrabbit OCM
>          Issue Type: Bug
>            Reporter: Sreekanth S Nair
>         Attachments: sreekanth_nair.vcf, sreekanth_nair.vcf
> I have an OCM class as given belwo
> @Node(jcrMixinTypes =JcrConstants.MIX_VERSIONABLE)
> public class XYZ  {
> @Field(path=true)
> private String path;
> @Field
> private String docContent;
> // and their closure methods
> }
> Then  i have created a root node as /domainName/moduleName 
> and set XYZ's  path value as /domainName/moduleName/documents.
> I can able to insert and update the XYZ  Objects successfully (i'm doing ocm  checkout
and checkin at object update time)
> but when try to get the version i'm always getting  root version (means the XYZ object
value on update  time). 
> I'm unable to get the base version (means the XYZ object value on insert time).
> If its not a bug...Please direct me how to extract version history. 
> fyi : i used
> ocm.getObject("/domainName/moduleName/documents","1.0") to get the value.
> i've worked based on apache jackrabbit OCM version mgmt site example but didn't work
for me.

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

View raw message