Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jdo-dev@db.apache.org
Date: Sat, 5 Mar 2011 09:10:46 +0000 (UTC)
From: "Andy Jefferson (JIRA)" <jira@apache.org>
To: jdo-dev@db.apache.org
Message-ID: <218006863.838.1299316246021.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1874741217.13401.1299232116890.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Updated: (JDO-678) Ability to set properties on
 PersistenceManager
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/JDO-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andy Jefferson updated JDO-678:
-------------------------------

    Attachment: jdo-678.patch

Proposed patch to PersistenceManager. I've called the new methods setProperty, getProperties, getSupportedProperties. Obviously since the PMF has "supportedOptions" and "getProperties" there may be other opinions, so welcome to suggestions that unify things

> Ability to set properties on PersistenceManager
> -----------------------------------------------
>
>                 Key: JDO-678
>                 URL: https://issues.apache.org/jira/browse/JDO-678
>             Project: JDO
>          Issue Type: Improvement
>          Components: api, specification, tck
>            Reporter: Andy Jefferson
>         Attachments: jdo-678.patch
>
>
> It would be desirable to be able to set properties on the PersistenceManager, so as to be able to configure/change behaviour for a PM. Currently the PM is generated with particular configuration (from the PMF) and allows specific options to be set. But what about vendor extensions ? Having a general setProperty/getProperty/getSupportedProperties would be useful, and could also encompass the existing detachAllOnCommit, IgnoreCache, etc settings.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira