From jdo-dev-return-3132-apmail-db-jdo-dev-archive=www.apache.org@db.apache.org Fri Feb 03 19:28:02 2006 Return-Path: Delivered-To: apmail-db-jdo-dev-archive@www.apache.org Received: (qmail 95471 invoked from network); 3 Feb 2006 19:28:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 3 Feb 2006 19:28:01 -0000 Received: (qmail 54835 invoked by uid 500); 3 Feb 2006 19:27:54 -0000 Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jdo-dev@db.apache.org Delivered-To: mailing list jdo-dev@db.apache.org Received: (qmail 54766 invoked by uid 99); 3 Feb 2006 19:27:53 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Feb 2006 11:27:50 -0800 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 4984E19B for ; Fri, 3 Feb 2006 20:27:17 +0100 (CET) Message-ID: <1512851937.1138994837297.JavaMail.jira@ajax.apache.org> Date: Fri, 3 Feb 2006 20:27:17 +0100 (CET) From: "Craig Russell (JIRA)" To: jdo-dev@db.apache.org Subject: [jira] Updated: (JDO-258) Write tests for new persistent-nontransactional-dirty lifecycle assertions In-Reply-To: <232609089.1134176229628.JavaMail.jira@ajax.apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/JDO-258?page=all ] Craig Russell updated JDO-258: ------------------------------ Fix Version: JDO 2 rc1 Version: JDO 2 beta > Write tests for new persistent-nontransactional-dirty lifecycle assertions > -------------------------------------------------------------------------- > > Key: JDO-258 > URL: http://issues.apache.org/jira/browse/JDO-258 > Project: JDO > Type: New Feature > Components: tck20 > Versions: JDO 2 beta > Reporter: Michelle Caisse > Assignee: Michael Watzek > Fix For: JDO 2 rc1 > > A5.6.2-3 [A persistent-nontransactional-dirty instance transitions to hollow if it is the parameter of evict or evictAll. This allows the application to remove instances from the set of instances whose state is to be committed to the datastore.] > A5.6.2-5 [The persistent-nontransactional-dirty instances will transition according to the RetainValues flag. With the RetainValues flag set to true, persistent-nontransactional-dirty instances will transition to persistent-nontransactional. With the RetainValues flag set to false, persistent-nontransactional-dirty instances will transition to hollow. ] > A5.6.2-7 [The persistent-nontransactional-dirty instances will transition according to the RestoreValues flag. With the RestoreValues flag set to true, persistent-nontransactional-dirty instances will make no state transition, but the fields will be restored to their values as of the beginning of the transaction, and any changes made within the transaction will be discarded. With the RestoreValues flag set to false, persistent-nontransactional-dirty instances will transition to hollow.] > A5.6.2-9 [The persistent-nontransactional-dirty instances will transition according to the RetainValues flag. With the RetainValues flag set to true, persistent-nontransactional-dirty instances will transition to persistent-nontransactional. With the RetainValues flag set to false, persistent-nontransactional-dirty instances will transition to hollow.] > A5.6.2-11 [With the RestoreValues flag set to true, persistent-nontransactional-dirty instances will make no state transition, but the fields will be restored to their values as of the beginning of the transaction, and any changes made within the transaction will be discarded. With the RestoreValues flag set to false, persistent-nontransactional-dirty instances will transition to hollow.] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira