Agenda:
1. Enhancer specification proposal. 1. -ecp is good but inconsistent in the text. 2. Should describe options in the same order as listed in both places. AI Craig write an enhancer Main class and upload to JIRA. Feedback needed from other experts.
2. Other issuesQuery.cancel changes have been checked in. Don't appear to be any issues. AI Craig update the spec and make clear the relationship between Query.cancel and multithreading (multithreaded flag doesn't need to be true to perform a Query.cancel).
How might an application dynamically tune itself by tracking field access by use-case? Need a few things: 1. identify which use case you're in; might have to analyze the stack frames at the time a use- case was needed, e.g. whenever an instance needed to be fetched or a query executed 2. associate a use case with a fetch plan 3. modify the fetch plan based on runtime experience, e.g. which fields were accessed by the use-case. AI Matthew discuss on email.
Action Items from weeks past:[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.
Craig L Russell Architect, Sun Java Enterprise System http://db.apache.org/jdo 408 276-5638 mailto:craig.russ...@sun.com P.S. A good JDO? O, Gasp!
smime.p7s
Description: S/MIME cryptographic signature
