Agenda:
1. JDO 2.2 plans: All items that we know about are filed in JIRA and assigned to the release 2.2. Any other issues should be brought up on email. It would be good to review the early of JSR-317 for ideas for the maintenance release.
2. Other issuesRichard is looking at JDO 1.1 RI to see if it can be adapted to use a memcached as a persistent store (instead of a backing store for another persistence layer).
Action Items from weeks past:[Apr 4 2008] AI Everyone who proposed a JDO 2.2 feature, please add a JIRA issue and assign it to a volunteer who will implement the feature.
[Feb 1 2008] AI Matthew see what would be needed to update the PMF contract to support ServiceLoader.
[Nov 30 2007] AI Christiaan propose more details on Update/copy by query for post-JDO 2.1.
[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.
[Aug 11 2006] AI Craig propose some semantics for behavior if user tries to add to a list where the ordering element is incorrect.
[Sep 2 2005] AI: To recruit members: Articles on TheServerSide directing attention to the site. T-shirts. 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
