Hi,

We will have our regular meeting Friday, February 17 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. Test status (Michael)
2. New tests status (Martin)
3. Other issues (any and all)

Action Items from weeks past:

[Feb 3 2005]  AI Michelle propose a release test plan and start a wiki
page.

[Feb 3 2005]  JDO-246 variable in the query result. AI Craig: update the
issue.

[Jan 20 2005] Debugging the regression we notice that some of the
foreign keys in the Company model have generated names which makes it
difficult to resolve the source of a key constraint violation.  Schema0
through schema4 are affected. AI: Michelle to fix the schema.  Done.

[Feb 3 2006] AI Michael W fix list of teardown classes in company  model
reader. JDO-285. But this fix cannot be checked in until JPOX  is fixed.

[Jan 20 2005]  AI Craig look at new life cycle tests to see if it can
fail at the end printing failure messages. AI Craig review the spec
updates to make sure the test is consistent. AI Craig: resolve the  test
case and spec issues.

[Jan 20 2005]   AI Michelle update the JDO releases page to point to
mirrors for download. AI Craig check in the released beta artifacts  to
the JDO maven repository (create a new releases directory parallel  to
trunk and branches).

[Jan 13 2005] AI Martin look at the enhancement tests for  completeness
(JDO-64).

[Jan 6 2005] AI: Michael: need to add a public static final field in  a
public class to test fully qualified class name static field in query.

[Dec 23 2005] Query tests (Michael B) Looking at JDO-194 errors on
Windows that don't happen on Linux. Might be a JRE bug. AI Martin  file
a Java bug so we know that there is a Java issue.

[Dec 23 2005] Fetch depth discussion: The spec needs more information
than is there in the PFD. AI Craig get more jdo experts involved in  the
discussion. In progress.

[Dec 9 2005]: Nontransactional write semantics appear to differ  between
optimistic and datastore transactions. Is this intentional?  AI: Craig
discuss with expert group. Done. It is intentional.
[Dec 2 2005] Inheritance 3 fails. Optimization of inheritance 1 where
there is no  table for abstract classes. JPOX doesn't support it. AI
Craig:  discuss this mapping with expert group. It might be an  optional
feature.

[Nov 18 2005] AI: BEA to sign the donation paperwork for their test
suite. Review how to merge their test cases into JDO TCK.

[Nov 4 2005] AI Martin: Update Martin's wiki with discusion of JDK   1.5
issues. in progress

[Oct 14 2005] AI: Michelle distill the mapping support that JPOX has
into a list of features that are/are not supported.

[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.

[July 29 2005] AI: Michelle Chapter 18 wiki needs to be updated to
include all JDO metadata elements and attributes. [not done]

April 15 2005] AI: Brian Topping will do the maven goal for creating
and uploading the snapshots. He will create a directory parallel to
trunk called "releases" and put the snapshots there.

[May 13 2005] AI: Brian Topping will arrange for automated nightly
builds.

[ Post a follow-up to this message ]

Attendees: Craig Russell, Michael Watzek, Michael Bouschen, Martin Zaun,
Michelle Caisse, Erik Bengtson.

Michelle Caisse wrote:

> 1. Test status (Michael)

1158 tests, 2 failures, 6 errors; 4/48 configurations fail. Inheritance
3 fails, and some query tests.  Implicit variable with the same name as
a class modulo case, elicits a new problem wherein generated SQL does
not execute on Derby. AI Michael B: file a JIRA.

> 2. New tests status (Martin)

Thread safety tests, expanding into four tests - Almost done with this,
testing tests.

> 3. Other issues (any and all)

Craig discussed timing for release candidate 1.  The first step is to
create a new branch, changing dependencies in project.xml.  api20, its
tests, dtd & xsd and tests, remaining chapter 18 issues being discussed
on the expert group should be complete before creating the release
branch.  AI Craig: file JIRA on Chapter 18 issues.  We will need a named
release of the RI that works with the JDO rc1.  Erik says the JPOX
release candidate will be called rc1.  Friday, February 24 is the day to
cut the release branch and have the RI available.

AI: Michael B to check in fixes to xsd and upload patch to JIRA for
tests. AI Craig: review schema tests.

Michael W. has updated .orm files, removing strategy attribute.  He
observes many errors during insert; JPOX tries to insert into an
identity column.
AI Eric: Investigate implementation's ability to use native identity
strategy given an identity column in the schema.
AI Craig: Discuss spec change involving native identity strategy with
expert group.
The meeting ended before discussion was complete on this issue.
Discussion will continue on email.

> Action Items from weeks past:
>
> [Feb 3 2005]  AI Michelle propose a release test plan and start a wiki
> page.

In progress.

>
> [Feb 3 2005]  JDO-246 variable in the query result. AI Craig: update
> the issue.

Done.

>
> [Feb 3 2006] AI Michael W fix list of teardown classes in company
> model reader. JDO-285. But this fix cannot be checked in until JPOX
> is fixed.
>
> [Jan 20 2005]  AI Craig look at new life cycle tests to see if it can
> fail at the end printing failure messages. AI Craig review the spec
> updates to make sure the test is consistent. AI Craig: resolve the
> test case and spec issues.
>
> [Jan 20 2005]   AI Michelle update the JDO releases page to point to
> mirrors for download.

Done.

> AI Craig check in the released beta artifacts  to the JDO maven
> repository (create a new releases directory parallel  to trunk and
> branches).
>
> [Jan 13 2005] AI Martin look at the enhancement tests for
> completeness (JDO-64).
>
> [Jan 6 2005] AI: Michael: need to add a public static final field in
> a public class to test fully qualified class name static field in query.
>
> [Dec 23 2005] Query tests (Michael B) Looking at JDO-194 errors on
> Windows that don't happen on Linux. Might be a JRE bug. AI Martin
> file a Java bug so we know that there is a Java issue.
>
> [Dec 23 2005] Fetch depth discussion: The spec needs more information
> than is there in the PFD. AI Craig get more jdo experts involved in
> the discussion. In progress.
>
> [Dec 9 2005]: Nontransactional write semantics appear to differ
> between optimistic and datastore transactions. Is this intentional?
> AI: Craig discuss with expert group. Done. It is intentional.
> [Dec 2 2005] Inheritance 3 fails. Optimization of inheritance 1 where
> there is no  table for abstract classes. JPOX doesn't support it. AI
> Craig:  discuss this mapping with expert group. It might be an
> optional feature.
>
> [Nov 18 2005] AI: BEA to sign the donation paperwork for their test
> suite. Review how to merge their test cases into JDO TCK.
>
> [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.
>
> [July 29 2005] AI: Michelle Chapter 18 wiki needs to be updated to
> include all JDO metadata elements and attributes. [not done]
>
> April 15 2005] AI: Brian Topping will do the maven goal for creating
> and uploading the snapshots. He will create a directory parallel to
> trunk called "releases" and put the snapshots there.
>
> [May 13 2005] AI: Brian Topping will arrange for automated nightly
> builds.


-- Michelle

[ Post a follow-up to this message ]

> Inheritance 3 fails

My understanding is that this test should only be run (or fail) if the JDO2
implementation has defined "javax.jdo.option.mapping.RelationSubclassTable" 
in
its PMF.supportedOptions(). JPOX does not include that option.
Can the test be updated to check on this ?
Want me to raise a JIRA ?

> We will need a named release of the RI that works with the JDO rc1. Erik says[/vbc
ol]
the JPOX[vbcol=seagreen]
> release candidate will be called rc1.  Friday, February 24 is the day to cut[/vbco
l]
the release branch[vbcol=seagreen]
> and have the RI available.

To be specific, the Maven details will be
groupId : jpox
artifactId : jpox, jpox-enhancer, jpox-dbcp, jpox-c3p0
version : 1.1.0-rc-1


--
Andy

[ Post a follow-up to this message ]

[ Post a follow-up to this message ]

Hi Craig,

>
> AI: Michael B to check in fixes to xsd and upload patch to JIRA for
> tests. AI Craig: review schema tests.
>
I checked in the jdo.xsd fixes (see revision 378770). From my point of
view jdo.xsd now accepts the same .jdo files as jdo.dtd. I checked the
jdo.dtd against the Feb-13 version of the spec. Both are identical,
except that the jdo.dtd has renamed the attribute fetch-depth to
recursion-depth already. Now we need to check the orm and jdoquery files.

I attached a new patch to JDO-202 including the current version of the
schema validation test (XMLTest). I copied Martin's message handling
changes to the AbstractTest class, so your JDO-309 comments apply here too.

Regards Michael

--
Michael Bouschen		Tech@Spree Engineering GmbH
mailto:mbo.tech@spree.de	http://www.tech.spree.de/
Tel.:++49/30/235 520-33		Buelowstr. 66
Fax.:++49/30/2175 2012		D-10783 Berlin

[ Post a follow-up to this message ]

[ Post a follow-up to this message ]

Hi Craig,

sorry, I have no idea what the problem is. Is it possible that you still
have an outdated test case or .jdo file that explicitly refers the
jdo.dtd file in the schema directory?

Regards Michael

> Hi Michael,
>
> Your update to the jdo.xsd fixed the earlier errors. But now I have
> this:
> 
>
>
> Clearly, this is the wrong location for the jdo.dtd file. The full
> error message is below. I probably did something wrong. Any ideas?
>
> Craig
> 
>
>
> Yippee. Three tests passed, and the following is probably a bonehead
> error of mine.
> 
>
>
> On Feb 18, 2006, at 2:15 PM, Michael Bouschen wrote:
> 
>
> Craig Russell
> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
> 408 276-5638 mailto:Craig.Russell@sun.com
> P.S. A good JDO? O, Gasp!
>


--
Michael Bouschen		Tech@Spree Engineering GmbH
mailto:mbo.tech@spree.de	http://www.tech.spree.de/
Tel.:++49/30/235 520-33		Buelowstr. 66
Fax.:++49/30/2175 2012		D-10783 Berlin

[ Post a follow-up to this message ]