[jira] Commented: (JDO-678) Ability to set properties on PersistenceManager
[ https://issues.apache.org/jira/browse/JDO-678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13002977#comment-13002977 ] Michael Bouschen commented on JDO-678: -- The patch looks good. Just one queston: what is the right return type for getProperties? The patch uses Map for PM.getProperties, where PMF.getProperties returns java.util.Properties. > 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 >Reporter: Andy Jefferson >Assignee: Andy Jefferson > Fix For: JDO 3 maintenance release 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. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (JDO-678) Ability to set properties on PersistenceManager
[ https://issues.apache.org/jira/browse/JDO-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-678: - Affects Version/s: JDO 3 Fix Version/s: JDO TCK challenge fixes JDO 3 maintenance release 1 Assignee: Andy Jefferson > 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 >Reporter: Andy Jefferson >Assignee: Andy Jefferson > Fix For: JDO 3 maintenance release 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. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (JDO-678) Ability to set properties on PersistenceManager
[ https://issues.apache.org/jira/browse/JDO-678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-678: - Fix Version/s: (was: JDO TCK challenge fixes) > 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 >Reporter: Andy Jefferson >Assignee: Andy Jefferson > Fix For: JDO 3 maintenance release 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. - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (JDO-678) Ability to set properties on PersistenceManager
[ 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
Re: Minutes: JDO TCK Conference Call Friday, Mar 4, 9 am Pacific Time
> 2. Typesafe ... query capability for JDOQL - ready for check-in?. > https://issues.apache.org/jira/browse/JDO-652 > Some questions: the factory for query instances: should it be PM or > PMF? Hint: do you really need to have the PM available in order to > build a query? The PM represents your current connection to the > database; the PMF represents the object model and mapping. To build a query you don't need the PM (but then to create a javax.jdo.Query object you don't really need a PM either :-P). To execute a (Query/)TypesafeQuery/TypedQuery you need a PM, and if you put constructor on the PMF then you have to pass the PM into the executeXXX methods. > Is there a bug in the blog? Yes there was, fixed thx. > JDO-678 Set properties on PersistenceManager > Seems like a good idea. Patch? Will do. Regards -- Andy DataNucleus (http://www.datanucleus.org)
