NOTE: Next phone meeting will be after the New Year, on Friday January 5, 2007.
Agenda:1. Moving forward with JDO maintenance release. Significant progress has been made on the items that were approved by the JCP. All of the updates that do not involve new APIs or new test cases have been made to the working draft of the 2.1 specification.
JDO-445 discussion. What about close()? Since the life cycle of the delegate is managed by the server, and the life cycle of the proxy is unbounded, close() should probably throw an exception. What about commit() and rollback()? Since the transaction is by definition managed by the server, these methods should throw an exception. Is the proxy for use only with JTA? Other possible use cases include "extended persistence context" within the server as well as Java SE. In these cases, where there is no TransactionSynchronizationRegistry assistance, a ThreadLocal would be needed, and the implementation is not as straightforward. For example, to support multiple PersistenceManagerFactories, a Map of pmf to pm would be needed in the ThreadLocal. And the API would need to be told which factory to use. AI Craig update the JIRA issue with this discussion.
The date issue has two components. One is to retrieve the date from the server, which could be done via JDOQL or simply an API on PersistenceManager or PersistenceManagerFactory. Another is to perform date arithmetic using queries such as to compare a date field with another date field plus 2 days. Both uses are in scope for the maintenance release. AI everyone reply to emails on this subject.
2. Other issuesLooking at the DTDs, they have a notation that they are actually xml. Should these be removed? AI everyone reply to JDO-454.
JDO-441 License update. Michael used the perl scripts on the Apache committers site and found a number of files with missing licenses. The scripts have already been updated to reflect the standard use of .jdo, .orm, and .jdoquery file name suffixes that are actually xml format. But .conf files used in tck are actually properties files, although this is just our usage pattern; there is nothing "standard" about this usage. AI Michael create a wiki page with the scripts used to update the files.
Action Items from weeks past:[Dec 15 2006] AI Michelle ask Bill Shannon if fscontext and providerutil will be available for automatic download from maven
[Oct 27 2006] AI: Matthew add comment to JDO-403 regarding split between JDO and ORM annotations..
[Sep 1 2006] AI Craig check into default handling to accommodate different defaults for annotations (?) based on context. In progress.
One idea is to use Strings for properties instead of boolean or int. This allows "default" to be a valid value, but requires a bit more work in the annotation handler and doesn't provide for compile-time checking of the values.
[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
