Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of vik002@gmail.com designates
 64.233.182.190 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=tme2p3Son9uGah48UoDEByzabqaOMjou2CB6ezI/29ctjGZtJJ4XLCguxf6Sa8kuj0dN76szvbuFzSHNtlVQQacnLBP4GM1haQi8RfsgLvxkGzqNrsCTRyLE9WtrdjHpBvr3tVMYBod9zivWgcHwhwb9J6TGIQ8lRRo4J3r9Qbg=
Message-ID: <33aff08b0711091218l30835a0nf2e619d0b19f5b56@mail.gmail.com>
Date: Fri, 9 Nov 2007 14:18:35 -0600
From: "Vikas Bhatia" <vik002@gmail.com>
To: users@jackrabbit.apache.org
Subject: changing property of a checked in node
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I have a node that is versionable. Here is the CND

===
[mcd:xy] > nt:base,mix:versionable
  orderable mixin
  - mcd:language (string) mandatory
  - mcd:url (string)
  - mcd:title (string) ignore mandatory

===

Here is the title is set to "ignore". After the node with this
nodetype xy is first created, we can change the title without checking
out the node. i.e., the title changing does not need the node to be
checked out.

But once a new version of node xy is created, lets say the new version
1.1, we cant change the property mcd:title without checking out the
node. if we try to change the title without checking out the node, the
error is

javax.jcr.version.VersionException: cannot set the value of a
checked-in node, /a/b/c/xyz:title

The behavior is confusing.. if the node is not versioned, you can
change the property, but once the first version is created, you
cannot... is that expected behavior. I thought that by setting the
title attribute to "ignore" you could change the property without
checking the node out.

Is this a bug or expected behavior?

V.