[
https://issues.apache.org/jira/browse/JDO-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13571405#comment-13571405
]
Andy Jefferson commented on JDO-678:
------------------------------------
Agree on what is returned from PM.getSupportedProperties.
Yes, making DataNucleus 3.2 (3.2.0.M4, or whichever is the current release in
that cycle at the time of the spec release) the RI for JDO3.1 is fine by me.
Anyone wanting DataNucleus 3.1.x can contribute their time etc to backdate my
change into the DN3.1 branch (usually enough to put people off ;-) )
> 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
> Affects Versions: JDO 3 (3.0)
> Reporter: Andy Jefferson
> Assignee: Craig L Russell
> Fix For: JDO 3 maintenance release 1 (3.1)
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
