Re: JDO TCK Conference Call Friday, May 20, 9 am PST
Hi Michelle, I cannot join the meeting today. This is my status: - Finished up with ri11 break out. Michael will check in new projects: core20, enhancer20, runtime20, query20, fostore20. fostore20 contains the testsuite. 2 Tests are contained in enhancer20. - Started work on JDO-48 (http://issues.apache.org/jira/browse/JDO-48). FYI: I'll have a day off on Monday. Regards, Michael Hi, We will have our regular meeting Friday, May 20 at 9 am PST to discuss JDO TCK issues and status. Dial-in numbers are: 866 230-6968 294-0479# International: +1 865 544-7856 Agenda: Test status (Michelle) Test cleanup fix (Michael W.) What is test/conf/JDOTCKTestCases.list for? (Michael B.) Detached objects (Matthew) Build dependency on cvs (Geoff) Apache accounts for Matthew and Eric (Craig) XML Schema (Brian T) JDO API release on ibiblio (Brian T) Other issues and status (any and all) -- Michelle -- --- Michael Watzek [EMAIL PROTECTED] Engineering GmbH mailto:[EMAIL PROTECTED]Buelowstr. 66 Tel.: ++49/30/235 520 36 10783 Berlin - Germany Fax.: ++49/30/217 520 12 http://www.spree.de/ ---
Minutes: JDO TCK Conference Call Friday, May 13, 9 am PST
Attendees: Michael Bouschen, Michael Watzek, Michelle Caisse, Matthew Adams, Martin Zaun, Craig Russell, Erik Bengtson, and Geoff Hendry. Our regular meeting was held Friday, May 13 at 9 am PST to discuss JDO TCK issues and status. Dial-in numbers are: 866 230-6968 294-0479# International: +1 865 544-7856 Agenda: 1. XML Schema (Brian T - specifics on orm dtd issues, Craig - dtd issues fixed?) Craig checked in changes to the jdo.dtd and orm.dtd. AI: Michelle will try the changes. 2. JDO API release on ibiblio (Brian T, Craig) no change to status. 3. Detached objects (Matthew) No committer badge. But no changes to code. AI: Craig to ask Geir where the committers' badges are for Matthew, Erik, and Michael Watzek. 4. Test development status (Michelle) Field types (collections and arrays too) are checked in. Need to figure out how to get metadata for SimpleClass read in first. Down to 82 errors, about 20 failures. Using beta3 which was just released. Takes a little over an hour to run tck20 compared to 15 minutes to run tck11. 5. Apache nightly builds (Brian) no change. 7. Other issues and status (any and all) Problem with splitting out runtime and query. org.apache.jdo.store defines the StoreManager interface and abstract StoreManagerImpl. They have references to the query package. Proposal is to move 4 interfaces in query having to do with QueryResult from query to runtime. Tortoise helps using svn with Windows. AI: Matthew send link to the site. We added foreign keys to the PCRect table and we have test case that tries to include null-valued PCPoints. This might be a test case bug. TestArrayColllections still fails with SimpleInterface[] and SimpleClass[] field types. AI: Erik to see if this is a test case bug or a JPOX issue. AI: Erik to try the tck without generating schema. What happens if the column attribute in field element conflicts with a column element? This is a spec issue for the experts to resolve. I guess it's an error. JSR 924 (Java SE 5 extensions) need to be examined to see their effect on the enhancer. AI: Martin to investigate and see about upgrading the ri11 to use the new extensions. Mahesh ported the ri11 enhancer to use ASM library instead of its own classfile library. Future project: to port the changes back to use in a future ri20 project. Geoff Hendry's implementation of JDO, JDOMax, has not yet run against the tck20. AI: Geoff try to get tck20 to run with JDOMax. 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
JIRA JDO-48
Hi, I like to propose a solution for JIRA JDO-48 (http://issues.apache.org/jira/browse/JDO-48). Actually, JDO-48 describes two issues: 1) Query tests fail cleaning up the database because of a foreign key constraint violation. The reason is that HollowInstanceMaintainsPK does not clean up the database. 2) Different TCK tests have different strategies for clean up. This proposal fixes issue 2) and, as a side effect, issue 1) also. Current status: Class JDOTest is the super class of all TCK tests. Amongst others, this class defines methods setUp() and tearDown(). Method setUp() creates the PMF instance. Method tearDown() closes the PM instance (created by tests) and it closes the PMF instance. Furthermore, method tearDown() implements the semantics that takes care for throwing the right exception in case of tests and/or tear down failures: Exceptions during tear down do not affect the test result in case of test failures. In such cases, method tearDown() logs exceptions. However, if tests succeed and tearDown() throws an exception then that exception determines the test result. Problem: Some tests override method tearDown() cleaning up the database, some tests clean up the database inside the test methods (testXXX). Proposal: The objective of this proposal are: 1) Tests should not need to override method tearDown() as the semantics is not trivial and error-prone. Instead, tests have hooks into setUp() and tearDown(). There, they may allocate/release resources and/or data. 2) Tests may register created (persistent) data. That data is cleaned up automatically during tearDown(). Solution: 1) We add 2 methods to class JDOTest localSetUp() and localTearDown(). These methods are called by setUp() and by tearDown(). They are hooks into the two methods and they may be overridden by subclasses. 2) Furthermore, we add 2 methods to class JDOTest which may be used for registering persistence capable instances and persistence capable classses. The default implementation of localTearDown() cleans up all registered persistent data. 3) We change all tests in order to comply to 1) and 2). Obviously, issue 3) is most time-consuming. For this reason, I suggest to solve 1) and 2) in a first step. In a second step, we solve issue 3) per TCK package, e.g. starting with org.apache.jdo.tck.lifecycle. What do you think? Regards, Michael -- --- Michael Watzek [EMAIL PROTECTED] Engineering GmbH mailto:[EMAIL PROTECTED]Buelowstr. 66 Tel.: ++49/30/235 520 36 10783 Berlin - Germany Fax.: ++49/30/217 520 12 http://www.spree.de/ ---
Re: JDO TCK Conference Call Friday, May 20, 9 am PST
Unfortunately I can't join in tomorrow. --- Michelle Caisse [EMAIL PROTECTED] wrote: Hi, We will have our regular meeting Friday, May 20 at 9 am PST to discuss JDO TCK issues and status. Dial-in numbers are: 866 230-6968 294-0479# International: +1 865 544-7856 Agenda: Test status (Michelle) Test cleanup fix (Michael W.) What is test/conf/JDOTCKTestCases.list for? (Michael B.) Detached objects (Matthew) Build dependency on cvs (Geoff) Apache accounts for Matthew and Eric (Craig) XML Schema (Brian T) JDO API release on ibiblio (Brian T) Other issues and status (any and all) -- Michelle Discover Yahoo! Get on-the-go sports scores, stock quotes, news and more. Check it out! http://discover.yahoo.com/mobile.html
