db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Craig L Russell <Craig.Russ...@Sun.COM>
Subject Correction: Minutes: JDO TCK Conference Call Friday, Feb 10, 9 am PST
Date Fri, 10 Feb 2006 19:42:08 GMT
Correction: Michael Watzek, Michelle Caisse, and Michael Bouschen  
also attended this meeting.


On Feb 10, 2006, at 11:35 AM, Craig L Russell wrote:

> Attendees: Martin Zaun, Craig Russell
> First, the news.
> Michelle Caisse and Michael Bouschen have been elected to the DB PMC.
> Congratulations to both of them for this vote of confidence in  
> their contributions.
> Agenda:
> 1. Test status (Michael) 1154 tests, 4 failures, 2 errors; 4 of 48  
> configurations fail. The errors are due to the joined subclass  
> strategy that JPOX does not support. The failures have JIRA issues  
> reported.
> 2. New tests status (Martin) The ThreadSafe class only tests one  
> multithread feature. The intent is to add three more methods to the  
> test to test that PersistenceManagerFactory.getPersistenceManager  
> is thread safe, and PersistenceManager.makePersistent on the same  
> instance is thread safe.
> A new JIRA JDO-299 has been added to add a signature test for the  
> jdo api jar. In case a vendor creates their own implementation of  
> the javax.jdo classes and interfaces, these need to be verified.  
> This is to cover the JCP requirement that the specified interfaces  
> must not be subsetted or supersetted.
> Martin has assigned several of the open new test cases to himself.
> 3. Other issues (any and all)
> Release planning: We're targeting the end of February to submit the  
> JSR 243 package to the JCP. The spec has to be final but the TCK  
> and RI don't have to be perfect. AI Craig: propose the release  
> schedule and details.
> JDO-246 There is a discussion about how to project Map and  
> Collection field types. Craig is inclined to disallow these. AI  
> Craig: respond to mail.
> Action Items from weeks past:
> [Feb 3 2005]  AI Michelle propose  a release test plan and start a  
> wiki page. Michelle has put a wiki called ReleaseTesting for  
> review. One issue is how to get coverage for platforms. We want to  
> put the platform under test (operating system, java version, etc.)  
> into the test results. AI Michelle work out how to do this.
> [Feb 3 2005]  Martin checked into the NoClassDefFoundError thrown  
> during  Class.forName. The result is that JDO implementations  
> should catch  not only ClassNotFoundException but in general  
> LinkageError. Any of  these Throwables should mean that the class  
> does not exist. This  issue came up during resolution of a name in  
> a JDOQL query. The JDO  implementation should use "class does not  
> exist" to indicate that the  name is not a class. JDO-194 has all  
> the details. AI Craig: update  the bug report and add a new test  
> method for this condition. Done.
> [Feb 3 2006] AI Michael W fix list of teardown classes in company   
> model reader. JDO-285. But this fix cannot be checked in until  
> JPOX  is fixed.
> [Jan 20 2005]  AI Craig look at new life cycle tests to see if it  
> can  fail at the end printing failure messages. AI Craig review the  
> spec  updates to make sure the test is consistent. AI Craig:  
> resolve the  test case and spec issues.
> [Jan 20 2005]   AI Michelle update the JDO releases page to point  
> to  mirrors for download. AI Craig check in the released beta  
> artifacts  to the JDO maven repository (create a new releases  
> directory parallel  to trunk and branches).
> [Jan 13 2005] AI Martin look at the enhancement tests for   
> completeness (JDO-64).
> [Jan 6 2005] AI: Michael: need to add a public static final field  
> in  a public class to test fully qualified class name static field  
> in query.
> [Dec 23 2005] Query tests (Michael B) Looking at JDO-194 errors on   
> Windows that don't happen on Linux. Might be a JRE bug. AI Martin   
> file a Java bug so we know that there is a Java issue.
> [Dec 23 2005] Fetch depth discussion: The spec needs more  
> information  than is there in the PFD. AI Craig get more jdo  
> experts involved in  the discussion. In progress. The spec has been  
> updated. Done.
> [Dec 9 2005]: Nontransactional write semantics appear to differ   
> between optimistic and datastore transactions. Is this  
> intentional?  AI: Craig discuss with expert group. Done. It is  
> intentional.
> [Dec 2 2005] Inheritance 3 fails. Optimization of inheritance 1  
> where  there is no  table for abstract classes. JPOX doesn't  
> support it. AI  Craig:  discuss this mapping with expert group. It  
> might be an  optional feature.
> [Nov 18 2005] AI: BEA to sign the donation paperwork for their  
> test   suite. Review how to merge their test cases into JDO TCK.
> [Nov 4 2005] AI Martin: Update Martin's wiki with discusion of  
> JDK   1.5 issues. in progress
> [Oct 14 2005] AI: Michelle distill the mapping support that JPOX  
> has into a list of features that are/are not supported.
> [Sep 2 2005] AI: To recruit members, update the web site. Articles   
> on  TheServerSide directing attention to the site. T-shirts, logo.   
> AI:  Craig write a ServerSide article.
> [July 29 2005] AI: Michelle Chapter 18 wiki needs to be updated  
> to   include all JDO metadata elements and attributes. [not done]
> April 15 2005] AI: Brian Topping will do the maven goal for  
> creating   and uploading the snapshots. He will create a directory  
> parallel to   trunk called "releases" and put the snapshots there.
> [May 13 2005] AI: Brian Topping will arrange for automated  
> nightly   builds.
> Craig Russell
> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
> 408 276-5638 mailto:Craig.Russell@sun.com
> P.S. A good JDO? O, Gasp!

Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!

View raw message