Re: JDO TCK Conference Call Friday, Aug 26, 9 am Pacific Time
I'd like to join. My skype id is matthewadams12. On Thu, Aug 25, 2011 at 9:53 PM, Michelle Caisse mcai...@sonic.net wrote: Hi, We will have our regular meeting Friday, August 26 at 9 am Pacific Time to discuss JDO TCK issues and status. The telecon will be held on Skype this week. Send your user id to the list if you would like to connect. Agenda: 1. Datastoreidentity detach test 2. JDOQL : Support for further methods (String, Enum, Date, JDOHelper): patch available https://issues.apache.org/**jira/browse/JDO-658https://issues.apache.org/jira/browse/JDO-658 3. Other issues Action Items from weeks past: [Aug 12 2011] AI Michael review the https://issues.apache.org/** jira/browse/JDO-658 https://issues.apache.org/jira/browse/JDO-658 patch in detail and update the JIRA description with all the tested methods. [Aug 12 2011] AI Craig review Apache POM build/release process for maven2 builds [Apr 08 2011] AI Craig comment on https://issues.apache.org/** jira/browse/JDO-617 https://issues.apache.org/jira/browse/JDO-617 re the utility of the update operator. -- Michelle -- @matthewadams12 mailto:matt...@matthewadams.me skype:matthewadams12 yahoo:matthewadams aol:matthewadams12 google-talk:matthewadam...@gmail.com msn:matt...@matthewadams.me http://matthewadams.me http://www.linkedin.com/in/matthewadams
Minutes: JDO TCK Conference Call Friday, Aug 26, 9 am Pacific Time
Note that next week's telecon is CANCELLED. Attendees: Michelle Caisse, Michael Bouschen, Matthew Adams 1. Datastoreidentity detach test Michael filed JIRA 68, and will start implementation. This involves changing the strategy from increment to sequence. We will then turn off the DataNucleus property AutoCreateTable. 2. JDOQL : Support for further methods (String, Enum, Date, JDOHelper): patch available https://issues.apache.org/jira/browse/JDO-658 Some test cases have been checked in, but several remain. Spec updates are also needed. Do we need support for enum now? We might want to add a new JIRA for some additional methods that we don't currently have support for and close the current issue. Michael will make suggestions for how to proceed. 3. Other issues Matthew noted that some customers require access to field or method version annotation, but JDO currently only permits version annotation specified at type level. He will file a JIRA for the extended functionality, currently supported by JPA and DataNucleus vendor extension. -- Michelle
[jira] [Created] (JDO-683) Allow version field/property to be visible to application
Allow version field/property to be visible to application - Key: JDO-683 URL: https://issues.apache.org/jira/browse/JDO-683 Project: JDO Issue Type: Improvement Components: api Affects Versions: JDO 3 maintenance release 1 Reporter: Matthew T. Adams Currently, it requires a vendor extension to make the version attribute (field or property) of a PC visible to the application. Some knowledgeable applications may need not only read access to the version field, but also write access to it. I propose that we allow version metadata to specify that a version attribute be application-visible. For annotation-based metadata, I recommend that it be allowed to be placed on fields methods. For XML metadata, add XML attributes attribute-name to the version element that allows the user to specify which field or property is to hold the application-visible version value. Along with this change would be verbiage in the spec noting that applications really shouldn't change this value, but a knowledgeable application may change it, based on a new PMF PM property called something like javax.jdo.option.OnVersionChangeByApplication with the following specified values. THROW: (default) the implementation will throw JDOUserVersionChangeException (extends JDOUserException) as early as the time the value is set, at the next flush, or at commit. IGNORE: the implementation ignores the value the user set for the object's version ALLOW: the implementation allows and uses the value the user set for the object's version This allows users to who know how their implementation behaves on user-modified version values to take advantage of such behavior. All names proposed are up for discussion. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
