Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jdo-dev@db.apache.org
Received-SPF: pass (athena.apache.org: domain of elindauer@gmail.com
 designates 66.249.92.174 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;
        b=fEKWm5d6/CfrR8safOLjpRjP4VojU5upBmdd0HtjtTg7Nja7Miu+016H5+kLUjRt3SCd830kq7lNN44RmpVBMKi0Y/Ig5wiSw/0zHOxcr+MyQ6ObLhhNgS1VXS0Mq8/koBTOh2G214BkF8lVGaNSLGvgVzT/yDNwFe5rlUn3LPM=
Message-ID: <d4e2c06a0710311343g5e60166csb680a3271ff50f6@mail.gmail.com>
Date: Wed, 31 Oct 2007 16:43:44 -0400
From: "Eric Lindauer" <elindauer@gmail.com>
To: jdo-dev@db.apache.org
Subject: feature request
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_9629_3988301.1193863424341"

------=_Part_9629_3988301.1193863424341
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi all,

Long time JDO user, first time poster.

I'd like to see JDO include a mechanism for accessing all the objects that
are:

a. enlisted in a particular transaction
b. managed by a particular persistence manager in it's level 1 cache

Either would do for my purposes, though I think they are both potentially
useful.  The most immediate need for these methods is to provide a mechanism
for an application to recognize when the data in a particular
PersistenceCapable object has changed, and make callbacks / refresh data /
etc.

I propose the following method signatures:

in javax.jdo.PersistenceManager:
    public Collection getManagedObjects();

in javax.jdo.Transaction:
    public Collection getEnlistedObjects();


Thanks for your consideration.  I apologize if I've written to the wrong
list.

     Sincerely,
      Eric Lindauer

------=_Part_9629_3988301.1193863424341--