[ 
https://issues.apache.org/jira/browse/JDO-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13671063#comment-13671063
 ] 

Craig L Russell commented on JDO-678:
-------------------------------------

Here's the latest spec update:

Property names might exactly match the names of the properties in 
javax.jdo.Constants or might differ in case only. For example, 
javax.jdo.Multithreaded is equivalent to    JAVAX.JDO.MultiThreaded or 
javax.jdo.multiTHREADED. 
Properties of the transaction associated with a persistence manager can be 
accessed via the named property in javax.jdo.Constants. For example, the 
non-transactional read property of the transaction can be accessed via 
javax.jdo.option.NontransactionalRead. 
Map<String, Object> getProperties();
A12.19-3 [Return a map of String, Object with the properties and values 
currently in effect. The keys in the map exactly match the corresponding names 
in javax.jdo.Constants.]


                
> 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

Reply via email to