Attendees: Michelle Caisse, Michael Bouschen, Craig Russell

Agenda:

1. Read-only datastore: There is an email thread on the topic of adding an option javax.jdo.ReadOnly. There are a few issues: what model object does the property belong on (Transaction, PersistenceManager, PersistenceManagerFactory); which operations might or are required to trigger an exception (makePersistent, deletePersistent, delete by query, flush with changed objects, commit with changed objects, optionally modify an instance); should a transaction be able to modify objects, add new objects, delete objects and then roll back; should we declare a new exception to be thrown, e.g. javax.jdo.JDOReadOnlyException?

AI: anyone with a strong opinion should create/update a JIRA. This is a candidate for a JDO 2.2 feature.

2. JDO 2.2 plans: Joerg raised an issue regarding bidirectional relationships, whether changes to one side of the relationship should immediately cause a change to the other side. We did discuss this during the JDO 2.1 cycle and concluded that there were some issues with this strategy. AI: Craig reply to Joerg and possibly update the spec to include the rationale.

Priority should be given to JDO 2.2 issues that require a spec change since these will have the most impact on the release schedule.

3. Other issues

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!

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to