Return-Path: Delivered-To: apmail-jackrabbit-users-archive@locus.apache.org Received: (qmail 74150 invoked from network); 9 Apr 2007 04:55:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Apr 2007 04:55:10 -0000 Received: (qmail 47266 invoked by uid 500); 9 Apr 2007 04:55:16 -0000 Delivered-To: apmail-jackrabbit-users-archive@jackrabbit.apache.org Received: (qmail 47247 invoked by uid 500); 9 Apr 2007 04:55:16 -0000 Mailing-List: contact users-help@jackrabbit.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@jackrabbit.apache.org Delivered-To: mailing list users@jackrabbit.apache.org Received: (qmail 47238 invoked by uid 99); 9 Apr 2007 04:55:16 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 08 Apr 2007 21:55:16 -0700 X-ASF-Spam-Status: No, hits=0.3 required=10.0 tests=MAILTO_TO_SPAM_ADDR,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of jukka.zitting@gmail.com designates 209.85.132.248 as permitted sender) Received: from [209.85.132.248] (HELO an-out-0708.google.com) (209.85.132.248) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 08 Apr 2007 21:55:09 -0700 Received: by an-out-0708.google.com with SMTP id d18so2087959and for ; Sun, 08 Apr 2007 21:54:48 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=a2GzIYI+xSSHFxldkk4S78IBlGlS6IAUnd+QhREkf2vEPQulAhrDMLvqLIDZx1l5rqnuN+2dYpsUfqY4QQBrudOZZHpKg0aF4YrPLG0+VPd3e1xk3kFWhLQvzwu4OcQhaUT3O+t0qF4JpOAqEb1OnzM1PABj/KaIb5fK2qNh4pY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=chYjm7kX7CX1EFmRTeVU0QBKbxSsGc2+b4hvpQa1XPQlkHZ13AJvhYE3ivV14phIPCCKta7NUJg1Qg/2zronPT7tWMZ6IxsN1QbrgpmDJIvVk1cylrYppXK90PcNGT0rzgEnn+VY5/kDhfB7aYBmgkyTZ4ovBWTR1jBqnKHcODY= Received: by 10.100.120.5 with SMTP id s5mr3717434anc.1176094488404; Sun, 08 Apr 2007 21:54:48 -0700 (PDT) Received: by 10.100.191.8 with HTTP; Sun, 8 Apr 2007 21:54:48 -0700 (PDT) Message-ID: <510143ac0704082154p55d52a94p939cc02bdeb24904@mail.gmail.com> Date: Mon, 9 Apr 2007 07:54:48 +0300 From: "Jukka Zitting" To: users@jackrabbit.apache.org Subject: Re: Setting JCR:CREATED Fails In-Reply-To: <396449.45608.qm@web55204.mail.re4.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <396449.45608.qm@web55204.mail.re4.yahoo.com> X-Virus-Checked: Checked by ClamAV on apache.org Hi, On 4/8/07, Julian wrote: > bump, anyone have thoughts on this? I see no reason to create a custom node > just so I can convert my data since the node type (jcr:created) already exists > and this would be a one time application. Any help is appreciated. I don't think there's any easy way to work around the protection of the jcr:created property. Even the XML import feature currently doesn't honor jcr:created values. I think it should (otherwise it's not good for backup/restore), so you may want to file a bug report against that. BR, Jukka Zitting