[
https://issues.apache.org/jira/browse/JDO-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13571389#comment-13571389
]
Craig L Russell commented on JDO-678:
-------------------------------------
I agree that setting properties should allow case-insensitive values. I'll
propose a spec change for this one.
My understanding was to allow the user to eschew property names entirely, by
using the defined names in javax.jdo.Constants, which is what the test case
does.
The reason for camel case property names is user friendliness. It's easier to
read DatastoreReadTimeoutMillis compared to datastorereadtimeoutmillis. So I
think it's wise to return the camel case name for pmf.supportedOptions (already
done), pm.supportedProperties, and pm.getProperties. Reviewing the discussion
above, there was never any discussion of lower-casing the values returned to
users.
Are you suggesting that we make DataNucleus 3.2 the RI for JDO 3.1? This is the
only issue that I know of with tck at this point.
> 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
