Sorry I wasn't on the call -- the family & I were camping for the holiday weekend and were out of range. Can someone tell me what the problem with the patch is? There was really nothing more to it than renaming ComponentMetadata to TypeMetadata and the associated ripples. EOL issue or some other?
On Fri, May 22, 2009 at 10:14 AM, Craig L Russell <craig.russ...@sun.com> wrote: > Attendees: Michael Bouschen, Michelle Caisse, Craig Russell > > Agenda: > > 1. New comments on MetaData specification API > https://issues.apache.org/jira/browse/JDO-615 > > This seems to be a good idea, since "component" is so overloaded, and "type" > has a specific meaning in Java. It's still ok to change since the API is > "early access" status. > > AI Everyone with an opinion: update the JIRA with your comments. > > The patch doesn't seem quite correct... > > 2. Other issues > > The instructions on how to release have been updated 22-May-2009 to include > instructions on synchronizing the m1-ibiblio-rsync-repository. > > Several changes are needed in the specification: > > There were a small number of cosmetic changes in the 2.3 specification, to > add a space after the ending period of sentences. Unfortunately, these are > marked as changes with change bars. > > Remove blank from before the fourth bullet p. 126. > > SerializeRead property description on p. 158 should state the effect on the > transaction mode (none) and on the connection (optimistic transaction will > retain the connection until the end of the transaction since the connection > holds the lock). > > Same discussion in the Query section on p. 171. We need to decide if the > SerializeRead property should be copied or serialized, so might need to > update section 14.5 on p. 167. > > The 2.3 versions of orm, jdoquery, and jdoconfig need to be updated in the > spec. The jdoquery should add the timeout option. The 2.3 version of jdo > also needs to add jdoquery timeout. What about the SerializeRead for the xml > versions of jdoquery? > > The query timeout needs to be added to the query metadata API p. 305. > > 27.4 The enhancer API is now defined so this paragraph needs to be edited. > > 27.5 The fetch plan API is now defined so this paragraph needs to be edited. > > 27.7 There are managed relationships so this paragraph needs to be edited. > > The footer for 2.3 EA still has the date May 8. > > Action Items from weeks past: > > [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. > > -- Michelle > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 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! > > -- mailto:matt...@matthewadams.me skype:matthewadams12 yahoo:matthewadams aol:matthewadams12 google-talk:matthewadam...@gmail.com msn:matt...@matthewadams.me http://matthewadams.me http://www.linkedin.com/in/matthewadams
