Attendees: Michelle Caisse, Michael Bouschen, Craig Russell
Agenda:1. Support for final modifier on fields. There are a few issues with making final fields persistent. First, the only difference between final and private is that final protects the class writer from accidentally changing the value of a final field; private protects the class writer from external code. Except in both cases, using reflection invalidates the protection. Second, the point at which the final field is modified by the jdo implementation would need to be carefully thought through. The final fields' values would have to be changed during specific life cycle events, such as retrieval from the datastore, flush, commit, rollback, etc. When exactly would the final fields be set? And how does this affect the memory model guarantees?
Bottom line: We'd like to see some more justification and discussion on the open questions raised above.
2. Test challenges. Some challenges have been filed by Ilan. Most have been fixed in 2.1 maintenance (trunk) and one of them is unresolved but can be fixed in the challenge resolution branch 2.0.1 interim to a final fix in 2.1 maintenance.
Clarification: The 2.1 maintenance work is being done on the trunk. We created a 2.0.1 branch that has no API changes from 2.0 but has fixes for the tck where a specification clarification or API change would be needed to pass the tck. A compliant JDO 2.0 implementation should be able to pass the latest tck test in the 2.0.1 branch.
3. Other issueshttp://issues.apache.org/jira/browse/JDO-534 Signature test doesn't work with JDK 6. Looks like the mechanism we use to check signatures has changed in an incompatible way from Java 5 to Java 6. Volunteer needed to check into this issue. It looks like the issue is running Java 5 jar files with Java 6 runtime. The signature test works fine if the api2 project is compiled with Java 6.
EvictAll: Michael created an issue http://issues.apache.org/jira/ browse/JDO-535 and updated the ChangeLog.
The tck2 currently fails due to database cleanup issues. Teardown fails. AI Michelle see if recently added tests have affected the teardown.
Action Items from weeks past: [Sep 14 2007] AI Matthew provide examples for 8.6.1.1 jdoconfig.xml. [June 22 2007] AI Craig discuss svn:eol-style on email.[June 22 2007] AI Craig write a proposal on annotation overrides for the expert group.
[May 25 2007] AI everyone Download the Grails demo from grails.org and check it out. Also look at Grails/Groovy ExpandoMetaClass that has the magic to avoid reflection and enhancement.
[May 25 2007] AI Matthew Adams prepare a proposal with just the basics of schema synchronization with jdo and orm metadata.
[May 18 2007] AI Craig update http://wiki.apache.org/jdo/ CurrentDevelopment wiki page
[Apr 27 2007] AI Craig review Query API and send email to experts.[Apr 27 2007] AI Erik file a JIRA regarding JPA style transactions and attach his discussion document to it.
[Mar 9 2007] AI Craig: Update the spec to require that the key of the listener is the class name of the listener, for consistency with proposed xml..
[Mar 2 2007] AI Craig: update the JDOHelper class to include a string constant "META-INF/jdo.xml" and a new method getPersistenceManagerFactory taking no arguments.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries to add to a list where the ordering element is incorrect.
[Jul 14 2006] AI: Erik document 220 annotations that don't have a corresponding JDO concept.
[Jun 23 2006] AI Martin look at what Hibernate and TopLink support for Enum types. In progress.
[Apr 14 2006] AI Craig: update the roadmap for JDO. In progress.[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK 1.5 issues. In progress
[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.
-- Michelle Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp!
smime.p7s
Description: S/MIME cryptographic signature
