Re: JDO TCK Conference Call Friday, Jun 24, 9 am PST

Michelle, I won't be able to attend the JDO meeting tomorrow, because of two other, one-time meetings that came up this week. Michael B., you probably also need to attend the EJB3 phone conference, which says "urgent" and just got scheduled for tomorrow 8 a.m. (it doesn't say how long it wil

Re: JDO TCK Conference Call Friday, Jun 24, 9 am PST

Hi, We will have our regular meeting Friday, June 24 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 (Michael W., Michelle) JPOX fixes/issues (Erik) Double-check locking in the PMF (Martin) D

Re: TestRunner remarks

Hi Michael, The performance boost is associated with using the jpox property org.jpox.identifier.defaultSchemaName to specify the schema in which the tables are installed. There is a performance boost whether the tables are installed in a named schema or the default schema when this property

IMPORTANT: New maven command line

Hi, I've just checked in the TestRunner project. There are now new maven goal names and command line options that you need to be aware of when you build or run the TCK. I've put a synopsis below (this information is also in trunk/README.txt); you may look at http://wiki.apache.org/jdo/TestR

Re: TestRunner remarks

Hi,Ok, then maybe we can prefix the log file names with database-app/dsid, e.g.derby-app-freeble-2005-06-17.logNaming conventions for "freeble" open for discussion...CraigOn Jun 23, 2005, at 9:35 AM, Michael Watzek wrote:Hi Craig, Hi,I hadn't thought of the multiple log file issue. For what it's wo

Re: TestRunner remarks

"one" invocation... Michelle Caisse wrote: I think that would be hard, since there is on invocation of BatchTestRunner, necessarily, per configuration. -- Michelle Craig Russell wrote: Hi, I hadn't thought of the multiple log file issue. For what it's worth, I'd prefer one log file for ea

Re: TestRunner remarks

Hi Craig, Hi, I hadn't thought of the multiple log file issue. For what it's worth, I'd prefer one log file for each configuration (app/datastore id; database) and not one log file for completeness/all test cases. We have in mind that there would be many completeness/all test cases configs,

Re: TestRunner remarks

I think that would be hard, since there is on invocation of BatchTestRunner, necessarily, per configuration. -- Michelle Craig Russell wrote: Hi, I hadn't thought of the multiple log file issue. For what it's worth, I'd prefer one log file for each configuration (app/datastore id; database

Re: TestRunner remarks

Hi,I hadn't thought of the multiple log file issue. For what it's worth, I'd prefer one log file for each configuration (app/datastore id; database) and not one log file for completeness/all test cases. We have in mind that there would be many completeness/all test cases configs, so it will be diff

Patch for ICompany package

Hi, please find the patch for the ICompany package attached. The patch creates a new package "org.apache.jdo.tck.pc.icompany" which contains the interfaces for the company model. Furthermore, it deletes the ICompany interface in the company package. Note: The patch does not add implements cla

Re: TestRunner remarks

Hi Michelle, Afterwards I ran "maven runtck.jdori". This runs 2 configurations - one for the completeness and one for all test cases. As a result, 4 log files are written to target/logs - 2 for application identity, 2 for datastore identity. The all test TCK runs produced the expected amount