Hi Michael,
On May 25, 2005, at 2:32 AM, Michael Watzek wrote:
Hi Craig,
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
Hi,
currently I'm running the TCK with the proposed implementation.
I realized that the TCK output does not show exception traces before all
tests have been executed. Instead, it only prints the execution status
of tests. After all tests have been executed, exception traces are
dumped. For
Hi Michael,
It makes sense. Try running with it and see if it is an improvement.
Michelle, what do you think?
Craig
On May 25, 2005, at 8:55 AM, Michael Watzek wrote:
Hi,
currently I'm running the TCK with the proposed implementation.
I realized that the TCK output does not show exception
Hi Michael,
On May 20, 2005, at 7:10 AM, Michael Watzek wrote:
Hi,
I like to propose a solution for JIRA JDO-48
(http://issues.apache.org/jira/browse/JDO-48).
Solution:
1) We add 2 methods to class JDOTest localSetUp() and localTearDown().
These methods are called by setUp
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
