Minutes: JDO TCK Conference Call Friday, Oct 14, 9 am Pacific Time
Attendees: Craig Russell, Matthew Adams Agenda: 1. Fix OSGi Export-Package entries https://issues.apache.org/jira/browse/JDO-684 Latest fix looks good. Resolve it. 2. JDO 3.0 dependency on JPA 3.0 (and 3.0.1) still depend on JPA 1.0. We decided that 3.1 did not allow use of JPA 2.0 and it doesn't make sense to continue to support JPA 1.0. Instead, we should just remove any dependency from JDO 3.0 API to JPA. Then, we should look at the tck to see if there are any code dependencies. 3. Other issues https://issues.apache.org/jira/browse/JDO-696 applies to both JDOHelper as well as IUT if the PMF is constructed directly with a new VendorPersistenceManagerFactory. Add api test case and tck test case for IUT case. Consider making private static void assertOnlyKnownStandardProperties(Map?, ? properties) public to allow IUT to use the method directly. Action Items from weeks past: [April 8 2011] AI Craig comment on https://issues.apache.org/jira/browse/JDO-617 re the utility of the update operator. [Sep 23 2011] AI Michael prepare spec update for JDOQL changes (JDO-658) and document restrictions on Enum.ordinal and Enum.toString. Create new JIRA for Math methods in JDOQL. [Sep 23 2011] AI Michael document when changing dependencies (to DataNucleus) it's necessary to rebuild the exectck project before running tck. Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp!
Re: Minutes: JDO TCK Conference Call Friday, Oct 14, 9 am Pacific Time
One minor clarification: On Fri, Oct 14, 2011 at 12:07 PM, Craig L Russell craig.russ...@oracle.com wrote: 2. JDO 3.0 dependency on JPA 3.0 (and 3.0.1) still depend on JPA 1.0. We decided that 3.1 did not allow use of JPA 2.0 and it doesn't make sense to continue to support JPA 1.0. Instead, we should just remove any dependency from JDO 3.0 API to JPA. Then, we should look at the tck to see if there are any code dependencies. This is true, except we are not removing JPA dependencies from JDO 3.0 or 3.0.1, only from JDO 3.1, which is represented by the trunk at the time of this writing. JDO 3.1 will not be dependent upon JPA 2.0, but JDO 2.0-3.0.1 will retain its dependence upon JPA 1.0. -matthew
Re: Minutes: JDO TCK Conference Call Friday, Oct 14, 9 am Pacific Time
On Fri, Oct 14, 2011 at 12:07 PM, Craig L Russell craig.russ...@oracle.com wrote: 3. Other issues https://issues.apache.org/jira/browse/JDO-696 applies to both JDOHelper as well as IUT if the PMF is constructed directly with a new VendorPersistenceManagerFactory. Add api test case and tck test case for IUT case. Consider making private static void assertOnlyKnownStandardProperties(Map?, ? properties) public to allow IUT to use the method directly. Actually, I think that this method might belong on JDOImplHelper. It's more of an SPI than an API, and I don't think an end user of JDOHelper would expect to see assertOnlyKnownStandardProperties. What do you say to moving it to JDOImplHelper and making it public there?
Re: Minutes: JDO TCK Conference Call Friday, Oct 14, 9 am Pacific Time
On Oct 14, 2011, at 12:27 PM, Matthew Adams wrote: One minor clarification: On Fri, Oct 14, 2011 at 12:07 PM, Craig L Russell craig.russ...@oracle.com wrote: 2. JDO 3.0 dependency on JPA 3.0 (and 3.0.1) still depend on JPA 1.0. We decided that 3.1 did not allow use of JPA 2.0 and it doesn't make sense to continue to support JPA 1.0. Instead, we should just remove any dependency from JDO 3.0 API to JPA. Then, we should look at the tck to see if there are any code dependencies. This is true, except we are not removing JPA dependencies from JDO 3.0 or 3.0.1, only from JDO 3.1, which is represented by the trunk at the time of this writing. JDO 3.1 will not be dependent upon JPA 2.0, but JDO 2.0-3.0.1 will retain its dependence upon JPA 1.0. My bad. remove any dependency from JDO 3.0 API to JPA s/3.0/3.1/ Craig -matthew Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp!
Re: Minutes: JDO TCK Conference Call Friday, Oct 14, 9 am Pacific Time
On Oct 14, 2011, at 12:31 PM, Matthew Adams wrote: On Fri, Oct 14, 2011 at 12:07 PM, Craig L Russell craig.russ...@oracle.com wrote: 3. Other issues https://issues.apache.org/jira/browse/JDO-696 applies to both JDOHelper as well as IUT if the PMF is constructed directly with a new VendorPersistenceManagerFactory. Add api test case and tck test case for IUT case. Consider making private static void assertOnlyKnownStandardProperties(Map?, ? properties) public to allow IUT to use the method directly. Actually, I think that this method might belong on JDOImplHelper. It's more of an SPI than an API, and I don't think an end user of JDOHelper would expect to see assertOnlyKnownStandardProperties. What do you say to moving it to JDOImplHelper and making it public there? Goo didea. Craig Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp!
Re: Minutes: JDO TCK Conference Call Friday, Oct 14, 9 am Pacific Time
Refactored attached patch. FYI, refactoring has spec ramifications. See https://issues.apache.org/jira/browse/JDO-696. On Fri, Oct 14, 2011 at 2:42 PM, Craig L Russell craig.russ...@oracle.com wrote: On Oct 14, 2011, at 12:31 PM, Matthew Adams wrote: On Fri, Oct 14, 2011 at 12:07 PM, Craig L Russell craig.russ...@oracle.com wrote: 3. Other issues https://issues.apache.org/jira/browse/JDO-696 applies to both JDOHelper as well as IUT if the PMF is constructed directly with a new VendorPersistenceManagerFactory. Add api test case and tck test case for IUT case. Consider making private static void assertOnlyKnownStandardProperties(Map?, ? properties) public to allow IUT to use the method directly. Actually, I think that this method might belong on JDOImplHelper. It's more of an SPI than an API, and I don't think an end user of JDOHelper would expect to see assertOnlyKnownStandardProperties. What do you say to moving it to JDOImplHelper and making it public there? Goo didea. Craig Craig L Russell Architect, Oracle http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@oracle.com P.S. A good JDO? O, Gasp! -- @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
JDO TCK Conference Call Friday, Oct 14, 9 am Pacific Time
Hi, We will have our regular meeting Friday, October 14 at 9 am Pacific Time to discuss JDO TCK issues and status. Dial-in numbers are: US Toll free: 866 682-4770 Germany Frankfurt 06916106 Germany Toll free: 08006648515 (Other countries by request) To place the call: 1. Call the toll free number. 2. Enter the conference number 939-3689# 3. Enter the security code # Agenda: 1. Fix OSGi Export-Package entries https://issues.apache.org/jira/browse/JDO-684 2. JDO 3.0 dependency on JPA 3. Other issues Action Items from weeks past: [April 8 2011] AI Craig comment on https://issues.apache.org/jira/browse/JDO-617 re the utility of the update operator. [Sep 23 2011] AI Michael prepare spec update for JDOQL changes (JDO-658) and document restrictions on Enum.ordinal and Enum.toString. Create new JIRA for Math methods in JDOQL. [Sep 23 2011] AI Michael document when changing dependencies (to DataNucleus) it's necessary to rebuild the exectck project before running tck.
