[ https://issues.apache.org/jira/browse/JDO-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13570867#comment-13570867 ]
Craig L Russell commented on JDO-678: ------------------------------------- I've got most of a test case written but have some questions that the DataNucleus team can probably sort. The supported options from persistence manager factory look fine: ... javax.jdo.option.DatastoreIdentity javax.jdo.option.mapping.JoinedTablePerConcreteClass javax.jdo.option.mapping.JoinedTablePerClass javax.jdo.option.LinkedList javax.jdo.option.Stack But the supported properties from persistence manager look hinky (modulo capitalization): ... javax.jdo.option.multithreaded javax.jdo.option.datastorereadtimeoutmillis javax.jdo.option.copyonattach ... >From the discussion here, I expected the supported properties to be: ... javax.jdo.option.Multithreaded javax.jdo.option.DatastoreReadTimeoutMillis javax.jdo.option.CopyOnAttach ... The property names are all documented at javax.jdo.Constants, e.g: static String PROPERTY_COPY_ON_ATTACH = "javax.jdo.option.CopyOnAttach"; The getProperties are consistent with getSupportedProperties but are not consistent with pm.supportedOptions and javax.jdo.Constants. I have no issues with the datanucleus property naming. > 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