Return-Path: Delivered-To: apmail-incubator-open-jpa-dev-archive@locus.apache.org Received: (qmail 42911 invoked from network); 7 Feb 2007 17:28:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 7 Feb 2007 17:28:27 -0000 Received: (qmail 69430 invoked by uid 500); 7 Feb 2007 17:28:34 -0000 Delivered-To: apmail-incubator-open-jpa-dev-archive@incubator.apache.org Received: (qmail 69271 invoked by uid 500); 7 Feb 2007 17:28:33 -0000 Mailing-List: contact open-jpa-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: open-jpa-dev@incubator.apache.org Delivered-To: mailing list open-jpa-dev@incubator.apache.org Received: (qmail 69250 invoked by uid 99); 7 Feb 2007 17:28:33 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Feb 2007 09:28:33 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Feb 2007 09:28:26 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id BA0837142BF for ; Wed, 7 Feb 2007 09:28:05 -0800 (PST) Message-ID: <19133390.1170869285759.JavaMail.jira@brutus> Date: Wed, 7 Feb 2007 09:28:05 -0800 (PST) From: "Patrick Linskey (JIRA)" To: open-jpa-dev@incubator.apache.org Subject: [jira] Created: (OPENJPA-128) Automatic cache pre-fill on server start MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Automatic cache pre-fill on server start ---------------------------------------- Key: OPENJPA-128 URL: https://issues.apache.org/jira/browse/OPENJPA-128 Project: OpenJPA Issue Type: New Feature Reporter: Patrick Linskey It'd be nice to have some means to automatically pre-fill the cache when a node starts up, either by copying from a different node or from a serialized image on disk, or by issuing some pre-specified queries. I really like the idea of just letting the user specify something like so: Although in that last example, we'd really want some way to specify a bit more detail about which pages of the data to use, as you would in single-string JDOQL. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.