You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jdo-dev@db.apache.org by Michelle Caisse <mc...@sonic.net> on 2010/06/11 06:03:47 UTC

JDO TCK Conference Call Friday, June 11, 9 am PDT

Hi,

We will have our regular meeting Friday, June 11 at 9 am PDT to
discuss JDO TCK issues and status.

Dial-in numbers are:
US Toll free: 866 682-4770
Germany Frankfurt  069222216106
Germany Toll free: 08006648515
(Other countries by request)

To place the call:
1. Call the toll free number.
2. Enter the conference number 939-3689#
3. Enter the security code 1111#

Agenda:

1. Tests in api2 for ... getPersistenceManagerFactory(Map,Map) - patch 
available for review. https://issues.apache.org/jira/browse/JDO-557
2. Other issues

Action Items from weeks past:

-- Michelle

Minutes: JDO TCK Conference Call Friday, June 18, 9 am PDT

Posted by Craig L Russell <cr...@oracle.com>.

Attendees: Michael Bouschen, Craig Russell

Agenda:

1. Tests in api2 for ... getPersistenceManagerFactory(Map,Map) - patch  
available for review. https://issues.apache.org/jira/browse/JDO-557  
Reviewed with a couple of comments; ok to check in.

2. Status of 3.0 release. Michelle has finished final formatting of  
the specification; Craig will check it over and send to JCP. The  
IssuesLog which is part of the new JSR maintenance process was created  
in the wiki.

Michael has a task to update the maven top level for 3.0.

3. Review JIRAs

JDO-519 is done with 3.0. AI Craig close this JIRA
JDO-615 is done. AI Craig close this JIRA
JDO-616 AI Craig look at this when reviewing the final book.

4. Other issues

JDO-580 looks like a bug in the disabled tests. Will be taken up for  
3.1.

Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!

Minutes: JDO TCK Conference Call Friday, June 25, 9 am PDT

Posted by Craig L Russell <cr...@oracle.com>.

Attendees: Michael Bouschen, Craig Russell

Agenda:

1. Status of 3.0 release.

Craig is building the 3.0 release. We will hold a vote to release the  
api and tck once the release is built.

Craig has submitted the spec to the JCP and is waiting for the project  
office.

2. Provision of a statically-typed refactor-friendly query capability  
for JDOQL https://issues.apache.org/jira/browse/JDO-652

Join the discussion on the JIRA! We just need to be mindful that this  
is a pretty big project.

3. Other issues

Moving parts of trunk to legacy. Discuss on mailing list. Probably  
should use a different term from legacy, since that term is already in  
use for JDK 1.4. Maybe archive or archive-trunk. Once we do this, we  
can adapt the maven.xml to remove the references to the old stuff.

Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!

Minutes: JDO TCK Conference Call Friday, July 2, 9 am PDT

Posted by Craig L Russell <cr...@oracle.com>.

For the record, I found this in my out-box...

Attendees: Michael Bouschen, Michelle Caisse, Craig Russell

Agenda:

1. Restructure JDO repository. Seems like the only issue is the name.  
It could be called jdo/trunk-archive or jdo/branches/archive-3.0 or  
something like this so we know that it's in the 3.0 time frame.

After the restructuring we will then change the version number in  
trunk to 3.1-SNAPSHOT.

2. JDO 3.0 staging release at http://people.apache.org/~clr/dist

Feedback from Andy: the pom.xml has the wrong version number. Thanks!

Michael points out that contrary to Craig's message, we do distribute  
the tck sources, just not via the maven repo.

Does anyone know how to make it easy to "attach sources" to an IDE? Is  
the current planned distribution via mirrors ok for this purpose? That  
is, if a user wants to look at the sources for a Maven dependency, is  
there a trivial way to "attach sources" within the IDE dialog if the  
user has not already downloaded the sources?

3. Other issues

none.

Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!

Minutes: JDO TCK Conference Call Friday, July 9, 9 am PDT

Posted by Craig L Russell <cr...@oracle.com>.

Attendees: Michelle Caisse, Michael Bouschen, Craig Russell

Agenda:

1. Vote on JDO 3.0 release. So far, so good. No neutral or negative  
votes. JIRA issues JDO-615 and JDO-619 are now resolved.

2. Provision of a ... query capability for JDOQL https://issues.apache.org/jira/browse/JDO-652 
  Looks promising, AI everyone please read and comment on this  
direction for JDOQL.

3. Other issues

Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!

Minutes: JDO TCK Conference Call Friday, July 16, 9 am PDT

Posted by Craig L Russell <cr...@oracle.com>.

NOTE: Due to holidays there will be no meeting next week. The next  
conference call is scheduled for July 30.

Attendees: Michael Bouschen, Michelle Caisse, Craig Russell

Agenda:

1. Next steps for JDO 3.0 release. The Apache DB PMC approved the  
release of the API and TCK artifacts. AI Craig publish the API and TCK  
artifacts on the Apache JDO web page.

The JCP EC is currently reviewing the maintenance release. You can  
follow the discussion on the JCP release approval at http://wiki.jcp.org/boards/index.php?b=jsr-243-public 
  (linked from http://jcp.org/aboutJava/communityprocess/maintenance/jsr243/index4.html 
  )

2. Missing DTD/XSD from SUN/Oracle website. The goal is to have the  
2.0, 2.1, 2.2 and 3.0 xsd and dtd artifacts published and downloadable  
from the site. AI Craig follow up with Oracle.

3. Fetch configuration. Looks like a good candidate for the next  
release. Continue discussion via JIRA and email. AI Andy file a JIRA  
(please).

4. Other issues.

Let's see if we can make a quicker spin for JDO 3.1. AI everyone look  
at the JIRA for 3.1 and "unscheduled" and discuss which issues should  
be in 3.1

Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!

Minutes: JDO TCK Conference Call Friday, July 30, 9 am PDT

Posted by Craig L Russell <cr...@oracle.com>.

Attendees: Michelle Caisse, Craig L Russell

Agenda:

The review period for JDO 3.0 in the JCP has ended. Waiting for  
official confirmation from JCP admin.

1. JDO 3.0 artifacts. The artifacts have been uploaded but don't yet  
have pointers from the jdo web site. AI Craig update the download page.

2. Missing DTD/XSD from SUN/Oracle website. Now that JDO 3.0 is out,  
Craig will get both the missing artifacts and the new artifacts  
uploaded.

3. JDO 3.next Nothing new this week.

4. Other issues

https://issues.apache.org/jira/browse/JDO-664 the upload of JDO 3.0  
artifacts resulted in the replacement of the jdo2-api metadata.xml  
with the new jdo-api metadata. This should not have happened since  
there are now two artifact-ids: jdo2-api and jdo-api. AI: Craig follow  
up with the Apache repository folks.

Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!

Minutes: JDO TCK Conference Call Friday, Aug 13, 9 am PDT

Posted by Craig L Russell <cr...@oracle.com>.

Attendees: Michael Bouschen, Craig Russell

Agenda:

1. Maven2 upgrade https://issues.apache.org/jira/browse/JDO-647 the  
new pom.xml for api and tck projects have been posted for review.

2. Other issues

Action Items from weeks past:

[6 Aug 10] AI Craig follow up on missing DTD/XSD in process

[6 Aug 10] AI Craig update the download page with JDO 3 artifacts done

[6 Aug 10] AI Craig talk to Apache PR re publicity for 3.0 release  
nothing yet

[6 Aug 10] AI Michael reply to a poster that we have a new release  
with a class missing from JDO 2.3 EA

-- Michelle













































Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!

Minutes: JDO TCK Conference Call Friday, Aug 20, 9 am PDT

Posted by Craig L Russell <cr...@oracle.com>.

Attendees: Michael Bouschen, Michelle Caisse, Craig Russell

Agenda:

1. Maven2 upgrade-  https://issues.apache.org/jira/browse/JDO-647.  
Making progress. Running mvn install with java 5 has a test case  
failure in the api project. Works fine on java 6. The changes to the  
api pom.xml in the jira look good.

The exectck mojo is under development. This maven plugin will be  
defined in the tck pom.xml to attach to a maven phase and run  
automatically. It will be configured by default in the tck pom.xml and  
can be overridden via additional elements in the tck pom.xml or by  
command line. For example, we might support -DinstallSchema to specify  
running the install schema function; -Dconf=mycnf to specify running  
only the configuration in the src/conf/mycnf.conf file; -Ddb=mysql to  
specify running with the database connection properties in the src/ 
conf/mysql.db file... The defaults will be to *not* install the  
schema, run all tests on the reference implementation with the derby  
database. Other possible scenarios would use different goals on the  
command line.

2. Other issues

Action Items from weeks past:

[6 Aug 10] AI Craig follow up on missing DTD/XSD. no news

[6 Aug 10] AI Craig update the download page with JDO 3 artifacts done.

[6 Aug 10] AI Craig talk to Apache PR re publicity for 3.0 release

It is possible to get publicity with Apache PR. What we need is  
something that makes a compelling story.

The best story is from users who can be quoted saying good things  
about the new functionality of the release.

Do we have any customers who are willing to be quoted? If not, do we  
have customers who can tell us a story (not a direct quote) about why  
the new features help them?

If not, we might not have anything worth a press release.

AI Everyone who knows of a customer who can tell us a story: tell us a  
story.

[6 Aug 10] AI Michael reply to a poster that we have a new release  
with a class missing from JDO 2.3 EA. no news

Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!

Minutes: JDO TCK Conference Call Friday, Aug 27, 9 am PDT

Posted by Craig L Russell <cr...@oracle.com>.

Attendees: Michelle Caisse, Michael Bouschen, Craig Russell

Agenda:

1. Maven2 upgrade-  https://issues.apache.org/jira/browse/JDO-647

Mojo will have multiple classes for different functions, e.g. enhance,  
installschema, runtck. Enhance would attach to the process-classes  
phase and the others to the integration-test phase.

Could use profiles to do a number of things in combination, e.g. run  
the tck on derby would be the standard specified in the pom but  
running the tck on mysql or oracle database could be a combination of  
properties specified in a profile. The mojo would be the same for all  
the profiles.

Invoking java programs from within the mojo can be as simple as  
invoking the static Main method of a named class. For example, if the  
installSchema goal needed to execute the program com.acme.script with  
command line parameters -Dfile=xyz you would have a line of java code:  
com.acme.script.Main(new String[] {"-Dfile=xyz"});

The properties that we use today to control the execution of the tck  
can be processed in a similar way by the mojo, which has access to the  
java system properties as well as the properties specified in the  
pom.xml in the mojo definition itself as well as profile properties.

2. Other issues

Mail regarding parameterized constructors. Michael will reply.

Mail regarding generate dynamic tables. This is a feature of  
implementations (e.g. DataNucleus).

Is the JDO 3.0 api jar file available via maven central?

Action Items from weeks past:

[6 Aug 10] AI Craig follow up on missing DTD/XSD. Still in progress.  
Might need to escalate.

Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!

Minutes: JDO TCK Conference Call Friday, Sep 17, 9 am PDT

Posted by Craig L Russell <cr...@oracle.com>.

Attendees: Michelle Caisse, Michael Bouschen, Craig Russell

Agenda:

1. Review patch for install schema portion of Maven2 upgrade -  https://issues.apache.org/jira/browse/JDO-647

The attached file seems to work. Making progress.

Could the progress of install schema be logged instead of sending  
messages to system output?

How would a user run the tck on an iut (implementation under test)?  
Probably choose the implementation via a property in the pom; also  
need to specify the name of the enhancer class as a property; both ri  
and iut should be made dependencies in the pom so they are  
automatically included in the class path of the tck executables.

2. Other issues

Possible candidates to be resolved for 3.1 (implemented or simply  
closed):

JDO-64 Enhancer test cases must be adapted to JDO2
JDO-71 Improve test cases in query.operators package
JDO-594 Add @Documented to all JDO Annotations
JDO-607 Require no-args constructor for PMF implementations and add  
static methods to PMF interface
JDO-632 Select new build/project tool
JDO-638 Add annotations for instance callbacks
JDO-643 avg return type
JDO-650 Support for conditional operator ? : in JDOQL
JDO-651 Modify specification to address NoSQL datastores

AI everyone review the other open issues and suggest resolutions

Action Items from weeks past:
[6 Aug 10] AI Craig follow up on missing DTD/XSD  (in progress)

Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!

Minutes: JDO TCK Conference Call Friday,Oct 8, 9 am PDT

Posted by Craig L Russell <cr...@oracle.com>.

Attendees: Michael Bouschen, Michelle Caisse, Craig Russell

Agenda:

1. Maven2 upgrade -
https://issues.apache.org/jira/browse/JDO-647
Making progress. Stuck on classpath issue. Maybe resolved; need to  
construct a class loader that contains the classes to enhance and the  
metadata loadable as resources.

2. Ability to specify positioning of field 'column(s)' in datastore  
"table" - patch being reviewed.
https://issues.apache.org/jira/browse/JDO-660
The 3.1 xsd and dtd files have been created. The patch adding the  
position can now be reviewed. Outstanding question about superclasses  
and how to reorder columns in subclasses.

3. List.get(int) support in JDOQL is missing - patch being reviewed.
https://issues.apache.org/jira/browse/JDO-633
Looks good. AI Michael review and respond to questions in jira.

4. Other issues

Action Items from weeks past:
[17 Sep 10] AI everyone review the other open issues and suggest  
resolutions
[6 Aug 10] AI Craig follow up on missing DTD/XSD
Resolved. All resources are now available on the web.

-- Michelle






























































Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!

Minutes: JDO TCK Conference Call Friday,Oct 15, 9 am PDT

Posted by Craig L Russell <cr...@oracle.com>.

Attendees: Michelle Caisse, Craig Russell

Agenda:

1. Maven2 upgrade -  https://issues.apache.org/jira/browse/JDO-647
Questions about enhancing and creating jar files. The enhancer isn't  
finding classes that have been put into the enhancer's class loader.  
Possibly need to have a parent class loader for the enhancer class  
loader. And it might be better to avoid the jar file but simply use  
directories for  class path entries.

2. JDO Querying reference.  AI everyone please see http://www.datanucleus.org/jdoql_quickref.pdf 
  and comment.

Action Items from weeks past:

[17 Sep 10] AI everyone review the other open issues and suggest  
resolutions for them.

Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!

Minutes: JDO TCK Conference Call Friday, Oct 22, 9 am PDT

Posted by Craig L Russell <cr...@oracle.com>.

Attendees: Matthew Adams, Michelle Caisse, Michael Bouschen, Craig  
Russell

Agenda:

1. Maven2 upgrade -  https://issues.apache.org/jira/browse/JDO-647.  
The classpath problem was resolved as a missing JDO_Test in the  
classpath. Everything that the enhancement needs must be on the  
classpath, including most of the TCK due to some TCK classes needing  
to be enhanced as persistence aware.

2. extend "sequence" metadata to allow specification of start and  
allocationSize. Patch for review. https://issues.apache.org/jira/browse/JDO-662

Looks good. AI Craig reply with review comments. Spec update needed.

3. Ability to specify positioning of field 'column(s)' in datastore  
"table" https://issues.apache.org/jira/browse/JDO-660

Looks good. Spec update needed.

4. Other issues

JDO repository has a jdo-api2 directory that is empty. Looks like a  
booboo. Gone.

Other projects like Objectify and Gora are intended to be JDO-lite  
implementations. Some comments from these other projects are that JDO  
"is complex". It would be worthwhile to take a look at these projects  
to see if an official JDO-lite would make sense. We already have a  
JIRA in place to track no-sql datastores.

https://issues.apache.org/jira/browse/JDO-663 Michael will refactor  
some of the tck tests to avoid duplication. Spec update also required.

Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!

Minutes: JDO TCK Conference Call Friday, Feb 25, 9 am Pacific Time

Posted by Craig L Russell <cr...@oracle.com>.

Attendees: Michael Bouschen, Michelle Caisse, Craig Russell

Agenda:

1. Typesafe ... query capability for JDOQL - ready for check-in?. https://issues.apache.org/jira/browse/JDO-652

We need more people than have looked at this to take a closer look.  
Volunteers? Michael, Craig. In particular, look at the TCK tests where  
we run the queries twice: once with String-based and one with the API.  
Adding a third option for the typesafe query would expose differences,  
mismatches.

http://www.datanucleus.org/products/accessplatform/jdo/jdoql_typesafe.html
http://datanucleus.blogspot.com/2010/11/jdo-typesafe-vs-jpa-criteria.html

2. Inheritance strategy that results in a table per class - patch  
provided. https://issues.apache.org/jira/browse/JDO-674

The patch looks good. Ok to check in.

3. Other issues

Dependency on JPA: The JIRA 675 to change tck pom dependency from  
Geronimo to Eclipse. Won't fix. There's no need.

Maven2 upgrade: Once we have it all working, we will remove the maven1  
support completely.

Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!

Minutes: JDO TCK Conference Call Friday, Mar 11, 9 am Pacific Time

Posted by Craig L Russell <cr...@oracle.com>.

Reminder: Next week the US will be on Daylight Savings Time.

Attendees: Michael Bouschen, Michelle Caisse, Matthew Adams, Craig  
Russell

Agenda:

1. Maven 2 upgrade - using setting.xml or profiles.xml for iut profile https://issues.apache.org/jira/browse/JDO-647

Try using a property like <tck.iut.classpath> in the exectck to set up  
the class path.

2. Typesafe ... query capability for JDOQL. https://issues.apache.org/jira/browse/JDO-652

A few method and class name issues that we should discuss and resolve.  
Quickly, please.

3. Ability to mark a class as read-only - https://issues.apache.org/jira/browse/JDO-677

Probably doing the check on flush is better.

4. query improvements: downcasting

There don't seem to be any issues here. Just need spec update and TCK  
test.

5. Other issues

Action Items from weeks past:

[Feb 25 2011] AI Michael, Craig, other volunteers: Look at  
Typesafe ... query capability for JDOQL https://issues.apache.org/jira/browse/JDO-652

Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!

Minutes: JDO TCK Conference Call Friday, Jan 14, 9 am Pacific Time

Posted by Craig L Russell <cr...@oracle.com>.

Attendees: Michael Bouschen, Michelle Caisse, Craig Russell

Agenda:

1. Maven2 upgrade.  https://issues.apache.org/jira/browse/JDO-647.  
Changes for parameterizing the version numbers are now checked in. Two  
issues remain:

Exception from new Derby version: is the generated SQL correct?  
Perhaps not. "Comparisons between 'BOOLEAN' and 'INTEGER' are not  
supported." AI Michael: file a JIRA to resolve whether this is a  
DataNucleus or Derby issue.

Upgrade to later DataNucleus version: using 2.1.1 now; need 2.2.2- 
SNAPSHOT for "average" change. AI Michelle: change the dependency for  
the project.

Next: see how to run the tck using an IUT (using profiles).

Also: how can we use the Apache maven release staging repository for  
releases? The idea is that the jdo-api could be defined as a maven  
dependency and automatically downloaded from the central repository  
but the jdo-tck needed to be installed as source. With the tck now  
defined as a maven2 project, should it also be usable as a dependency?  
Probably no change to the current practice, since the tck is intended  
to be executed by itself with no user code involved.

2. Other issues

Action items from past meetings: Craig check into using the Apache  
parent pom

Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!

Re: Query test failure with newer derby version (was Re: Minutes: JDO TCK Conference Call Friday, Jan 7, 9 am Pacific Time)

Posted by Michael Bouschen <mb...@spree.de>.

Hi,

this is the JDOQL query:
   SELECT FROM org.apache.jdo.tck.pc.mylib.PCPoint EXCLUDE SUBCLASSES
   WHERE (x == 2) == true
and here is the generated SQL:
   SELECT 'org.apache.jdo.tck.pc.mylib.PCPoint' AS 
NUCLEUS_TYPE,A0.ID,A0.X,A0.Y
   FROM APPLICATIONIDENTITY0.PCPOINT A0
   WHERE A0.X = 2 = 1

So the question is: what does SQL define when comparing an integer and a 
boolean?
The expression "A0.X = 2" evaluates to a boolean which is then compared 
to the integer 1.

Regards Michael

> Hi Craig,
>
> [...]
>>>
>>> (2) query test:
>>>
>>> The failing test is in jdoql.conf: class 
>>> org.apache.jdo.tck.query.jdoql.ParenthesesMarkOperatorPrecedence 
>>> method runTestParenthesesMarkOperatorPrecedence08.
>>> The test runs a JDOQL query with PCPoint as candidate class and "(x 
>>> == 2) == true" as filter. It results in an exception thrown by the 
>>> derby SQL compiler:
>>>
>>> java.sql.SQLException: Comparisons between 'BOOLEAN' and 'INTEGER' 
>>> are not supported. Types must be comparable. String types must also 
>>> have matching collation. If collation does not match, a possible 
>>> solution is to cast operands to force them to the default collation 
>>> (e.g. SELECT tablename FROM sys.systables WHERE CAST(tablename AS 
>>> VARCHAR(128)) = 'T1')
>>>
>>> The derby versions 10.6.1.0 and 10.7.1.1 run into this exception. 
>>> But it does NOT happen with derby version 10.4.2.0, which we are 
>>> using in the maven1 environment.
>>
>> Good catch. Would you have time to file a JIRA with Derby?
>
> First I want to take a look at the generated SQL before filing a JIRA. 
> I'll keep you posted.
>
> Regards Michael
>
> [...]
>


-- 
*Michael Bouschen*
*Prokurist*

akquinet tech@spree GmbH
Bülowstr. 66, D-10783 Berlin

Fon:   +49 30 235 520-33
Fax:   +49 30 217 520-12
Email: michael.bouschen@akquinet.de
Url: www.akquinet.de <http://www.akquinet.de>

akquinet tech@spree GmbH, Berlin
Geschäftsführung: Martin Weber, Prof. Dr. Christian Roth
Amtsgericht Berlin-Charlottenburg HRB 86780 B
USt.-Id. Nr.: DE 225 964 680

Query test failure with newer derby version (was Re: Minutes: JDO TCK Conference Call Friday, Jan 7, 9 am Pacific Time)

Posted by Michael Bouschen <mb...@spree.de>.

Hi Craig,

[...]
>>
>> (2) query test:
>>
>> The failing test is in jdoql.conf: class 
>> org.apache.jdo.tck.query.jdoql.ParenthesesMarkOperatorPrecedence 
>> method runTestParenthesesMarkOperatorPrecedence08.
>> The test runs a JDOQL query with PCPoint as candidate class and "(x 
>> == 2) == true" as filter. It results in an exception thrown by the 
>> derby SQL compiler:
>>
>> java.sql.SQLException: Comparisons between 'BOOLEAN' and 'INTEGER' 
>> are not supported. Types must be comparable. String types must also 
>> have matching collation. If collation does not match, a possible 
>> solution is to cast operands to force them to the default collation 
>> (e.g. SELECT tablename FROM sys.systables WHERE CAST(tablename AS 
>> VARCHAR(128)) = 'T1')
>>
>> The derby versions 10.6.1.0 and 10.7.1.1 run into this exception. But 
>> it does NOT happen with derby version 10.4.2.0, which we are using in 
>> the maven1 environment.
>
> Good catch. Would you have time to file a JIRA with Derby?

First I want to take a look at the generated SQL before filing a JIRA. 
I'll keep you posted.

Regards Michael

[...]

-- 
*Michael Bouschen*
*Prokurist*

akquinet tech@spree GmbH
Bülowstr. 66, D-10783 Berlin

Fon:   +49 30 235 520-33
Fax:   +49 30 217 520-12
Email: michael.bouschen@akquinet.de
Url: www.akquinet.de <http://www.akquinet.de>

akquinet tech@spree GmbH, Berlin
Geschäftsführung: Martin Weber, Prof. Dr. Christian Roth
Amtsgericht Berlin-Charlottenburg HRB 86780 B
USt.-Id. Nr.: DE 225 964 680

Re: Minutes: JDO TCK Conference Call Friday, Jan 7, 9 am Pacific Time

Posted by Craig L Russell <cr...@oracle.com>.

Hi Michael,

On Jan 8, 2011, at 2:33 AM, Michael Bouschen wrote:

> Hi,
>> Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
>>
>> Agenda:
>>
>> 1. Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647
>>
>> Only two tests are now failing: signature test and a query test.  
>> The signature test might be reading the wrong signature file, since  
>> there have been a few changes to the signature since 3.0.
>
> I looked at the test failures:
>
> (1) signature test:
>
> The current pom.xml still refers the 3.0 version of jdo-api. The  
> test succeeds after switching the dependency to 3.1-SNAPSHOT.
>
> Please note the dependency needs to be changed in exectck and tck!
>
> (2) query test:
>
> The failing test is in jdoql.conf: class  
> org.apache.jdo.tck.query.jdoql.ParenthesesMarkOperatorPrecedence  
> method runTestParenthesesMarkOperatorPrecedence08.
> The test runs a JDOQL query with PCPoint as candidate class and "(x  
> == 2) == true" as filter. It results in an exception thrown by the  
> derby SQL compiler:
>
> java.sql.SQLException: Comparisons between 'BOOLEAN' and 'INTEGER'  
> are not supported. Types must be comparable. String types must also  
> have matching collation. If collation does not match, a possible  
> solution is to cast operands to force them to the default collation  
> (e.g. SELECT tablename FROM sys.systables WHERE CAST(tablename AS  
> VARCHAR(128)) = 'T1')
>
> The derby versions 10.6.1.0 and 10.7.1.1 run into this exception.  
> But it does NOT happen with derby version 10.4.2.0, which we are  
> using in the maven1 environment.

Good catch. Would you have time to file a JIRA with Derby?

Thanks,

Craig
>
> Regards Michael
>>
>> Maven now has a process for publishing Apache artifacts. We should  
>> look into what is needed to use the staging and publishing  
>> repositories.
>>
>> 2. Other issues
>>
>> https://issues.apache.org/jira/browse/JDO-643 should add the tck as  
>> an affected component. We should also add test cases for average of  
>> more of the types that we support, including BigDecimal and  
>> BigInteger.
>>
>> https://issues.apache.org/jira/browse/JDO-671 The Oracle.com JDO  
>> page needs an update.
>>
>> Action Items from weeks past:
>>
>> Craig L Russell
>> Architect, Oracle
>> http://db.apache.org/jdo
>> 408 276-5638 mailto:Craig.Russell@oracle.com
>> P.S. A good JDO? O, Gasp!
>>
>
>
> -- 
> *Michael Bouschen*
> *Prokurist*
>
> akquinet tech@spree GmbH
> Bülowstr. 66, D-10783 Berlin
>
> Fon:   +49 30 235 520-33
> Fax:   +49 30 217 520-12
> Email: michael.bouschen@akquinet.de
> Url: www.akquinet.de <http://www.akquinet.de>
>
> akquinet tech@spree GmbH, Berlin
> Geschäftsführung: Martin Weber, Prof. Dr. Christian Roth
> Amtsgericht Berlin-Charlottenburg HRB 86780 B
> USt.-Id. Nr.: DE 225 964 680
>
> -- 
> *Michael Bouschen*
> *Prokurist*
>
> akquinet tech@spree GmbH
> Bülowstr. 66, D-10783 Berlin
>
> Fon:   +49 30 235 520-33
> Fax:   +49 30 217 520-12
> Email: michael.bouschen@akquinet.de
> Url: www.akquinet.de <http://www.akquinet.de>
>
> akquinet tech@spree GmbH, Berlin
> Geschäftsführung: Martin Weber, Prof. Dr. Christian Roth
> Amtsgericht Berlin-Charlottenburg HRB 86780 B
> USt.-Id. Nr.: DE 225 964 680

Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!

Re: Minutes: JDO TCK Conference Call Friday, Jan 7, 9 am Pacific Time

Posted by Michael Bouschen <mb...@spree.de>.

Hi,
> Attendees: Michael Bouschen, Michelle Caisse, Craig Russell
>
> Agenda:
>
> 1. Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647
>
> Only two tests are now failing: signature test and a query test. The 
> signature test might be reading the wrong signature file, since there 
> have been a few changes to the signature since 3.0.

I looked at the test failures:

(1) signature test:

The current pom.xml still refers the 3.0 version of jdo-api. The test 
succeeds after switching the dependency to 3.1-SNAPSHOT.

Please note the dependency needs to be changed in exectck and tck!

(2) query test:

The failing test is in jdoql.conf: class 
org.apache.jdo.tck.query.jdoql.ParenthesesMarkOperatorPrecedence method 
runTestParenthesesMarkOperatorPrecedence08.
The test runs a JDOQL query with PCPoint as candidate class and "(x == 
2) == true" as filter. It results in an exception thrown by the derby 
SQL compiler:

  java.sql.SQLException: Comparisons between 'BOOLEAN' and 'INTEGER' are 
not supported. Types must be comparable. String types must also have 
matching collation. If collation does not match, a possible solution is 
to cast operands to force them to the default collation (e.g. SELECT 
tablename FROM sys.systables WHERE CAST(tablename AS VARCHAR(128)) = 'T1')

The derby versions 10.6.1.0 and 10.7.1.1 run into this exception. But it 
does NOT happen with derby version 10.4.2.0, which we are using in the 
maven1 environment.

Regards Michael
>
> Maven now has a process for publishing Apache artifacts. We should 
> look into what is needed to use the staging and publishing repositories.
>
> 2. Other issues
>
> https://issues.apache.org/jira/browse/JDO-643 should add the tck as an 
> affected component. We should also add test cases for average of more 
> of the types that we support, including BigDecimal and BigInteger.
>
> https://issues.apache.org/jira/browse/JDO-671 The Oracle.com JDO page 
> needs an update.
>
> Action Items from weeks past:
>
> Craig L Russell
> Architect, Oracle
> http://db.apache.org/jdo
> 408 276-5638 mailto:Craig.Russell@oracle.com
> P.S. A good JDO? O, Gasp!
>


-- 
*Michael Bouschen*
*Prokurist*

akquinet tech@spree GmbH
Bülowstr. 66, D-10783 Berlin

Fon:   +49 30 235 520-33
Fax:   +49 30 217 520-12
Email: michael.bouschen@akquinet.de
Url: www.akquinet.de <http://www.akquinet.de>

akquinet tech@spree GmbH, Berlin
Geschäftsführung: Martin Weber, Prof. Dr. Christian Roth
Amtsgericht Berlin-Charlottenburg HRB 86780 B
USt.-Id. Nr.: DE 225 964 680

-- 
*Michael Bouschen*
*Prokurist*

akquinet tech@spree GmbH
Bülowstr. 66, D-10783 Berlin

Fon:   +49 30 235 520-33
Fax:   +49 30 217 520-12
Email: michael.bouschen@akquinet.de
Url: www.akquinet.de <http://www.akquinet.de>

akquinet tech@spree GmbH, Berlin
Geschäftsführung: Martin Weber, Prof. Dr. Christian Roth
Amtsgericht Berlin-Charlottenburg HRB 86780 B
USt.-Id. Nr.: DE 225 964 680

Minutes: JDO TCK Conference Call Friday, Jan 7, 9 am Pacific Time

Posted by Craig L Russell <cr...@oracle.com>.

Attendees: Michael Bouschen, Michelle Caisse, Craig Russell

Agenda:

1. Maven2 upgrade.  https://issues.apache.org/jira/browse/JDO-647

Only two tests are now failing: signature test and a query test. The  
signature test might be reading the wrong signature file, since there  
have been a few changes to the signature since 3.0.

Maven now has a process for publishing Apache artifacts. We should  
look into what is needed to use the staging and publishing repositories.

2. Other issues

https://issues.apache.org/jira/browse/JDO-643 should add the tck as an  
affected component. We should also add test cases for average of more  
of the types that we support, including BigDecimal and BigInteger.

https://issues.apache.org/jira/browse/JDO-671 The Oracle.com JDO page  
needs an update.

Action Items from weeks past:

Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!

Minutes: JDO TCK Conference Call Friday, Dec 17, 9 am Pacific Time

Posted by Craig L Russell <cr...@oracle.com>.

PLEASE NOTE: JDO will be on winter break for the next two weeks. Next  
meeting: January 7, 2011

Attendees: Michael Bouschen, Michelle Caisse, Craig Russell

Agenda:

1. Maven2 upgrade.  https://issues.apache.org/jira/browse/JDO-647.

Mostly done but not completely working. Need to update the version  
numbers in the pom to be identical to those used in maven 1. Some  
tests cannot find the test data resource. The test data reader is  
calling the constructor for the spring xmlbeans reader which cannot  
find the file. Class path issue?

2. Avg return type - patch available for review https://issues.apache.org/jira/browse/JDO-643

This proposes that integral types and floating point types all return  
double for average. Is there a good reason for JDO to be different  
from JPA? AI Craig: update JIRA with comment

3. Extend PersistenceManageFactory to return all known entity classes - 
new comments https://issues.apache.org/jira/browse/JDO-667

4. Other issues

Take a look at http://www.datanucleus.org/servlet/forum/viewthread_thread,6467 
  for an interesting idea.

Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!

Re: JDO TCK Conference Call Friday, Dec 17, 9 am Pacific Time

Posted by Craig L Russell <cr...@oracle.com>.

PLEASE NOTE: JDO will be on winter break for the next two weeks. Next  
meeting: January 7, 2011

Attendees: Michael Bouschen, Michelle Caisse, Craig Russell

Agenda:

1. Maven2 upgrade.  https://issues.apache.org/jira/browse/JDO-647.

Mostly done but not completely working. Need to update the version  
numbers in the pom to be identical to those used in maven 1. Some  
tests cannot find the test data resource. The test data reader is  
calling the constructor for the spring xmlbeans reader which cannot  
find the file. Class path issue?

2. Avg return type - patch available for review https://issues.apache.org/jira/browse/JDO-643

This proposes that integral types and floating point types all return  
double for average. Is there a good reason for JDO to be different  
from JPA? AI Craig: update JIRA with comment

3. Extend PersistenceManageFactory to return all known entity classes - 
new comments https://issues.apache.org/jira/browse/JDO-667

4. Other issues

Take a look at http://www.datanucleus.org/servlet/forum/viewthread_thread,6467 
  for an interesting idea.

Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!

JDO TCK Conference Call Friday, Dec 3, 9 am Pacific Time

Posted by Craig L Russell <cr...@oracle.com>.

Attendees: Michelle Caisse, Matthew Adams, Michael Bouschen, Craig  
Russell

Agenda:

1. Maven2 upgrade.  https://issues.apache.org/jira/browse/JDO-647

Good progress. No hang any longer. Getting the schema loaded. But not  
quite working yet. Some tables are not created. Signature test  
complains.

2. Other issues

There's a project called naked objects which is now incubating as  
Apache Isis. How about a JDO store for the objects?
Check it out: https://issues.apache.org/jira/browse/ISIS-14

Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!

Re: JDO TCK Conference Call Friday, Nov12, 9 am PDT

Posted by Craig L Russell <cr...@oracle.com>.

Attendees: Matthew Adams, Michelle Caisse, Michael Bouschen, Craig  
Russell

Agenda:

1. Maven2 upgrade - patch posted with enhance goal.  https://issues.apache.org/jira/browse/JDO-647

We can put the version numbers into the parent pom. Starting with  
dependencies but we can also put the version number of the components  
into the parent pom.

The runtck goal is mostly running. Cannot create a connection with the  
underlying database.

2. Other issues

Action Items from weeks past:
[17 Sep 10] AI everyone review the other open issues and suggest  
resolutions

Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!

Minutes: JDO TCK Conference Call Friday, Jan 21, 9 am Pacific Time

Posted by Craig L Russell <cr...@oracle.com>.

Attendees: Michelle Caisse, Michael Bouschen, Craig Russell

Agenda:

1. Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647

Dependencies have been changed to conform to the maven
DependencyManagement pattern.
Tck dependencies have been updated to the latest DataNucleus version
2.2.2. The dependency should actually be on the exectck project not
the tck project.
To run the tck with an IUT, users will have to edit the pom and
profiles to add their dependent jar files.
The "run-once" tests run twice. Is this ok? Yes.

2. Inheritance strategy http://mail-archives.apache.org/mod_mbox/db-jdo-dev/201101.mbox/browser

Surprising to hear that JPA has a mapping feature that JDO doesn't.
Maybe there is a misunderstanding. AI everyone: Is this scenario
really not supported by JDO?

3. Test case failure: SQLException in
ParenthesesMarkOperatorPrecedence https://issues.apache.org/jira/browse/JDO-672

No progress.

4. Other issues

Dependencies on JPA: the api needs JPA 3.0 and the tck needs JPA 2.0

The issue is with the getProperties() method in
JDOEntityManagerFactory which extends both EntityManagerFactory and
PersistenceManagerFactory. In JDO PersistenceManagerFactory the method
returns Properties and in JPA EntityManagerFactory returns Map<String,
Object>.

Possible solutions: change JDO PersistenceManagerFactory to return
Map<String, Object> or remove the JDOEntityManagerFactory and
JDOEntityManger interfaces. Are these being used by anyone?

AI Michael file a JIRA.

Action Items from weeks past:

[Jan 14 2011] Craig check into using the Apache parent pom. No progress.

Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!

Minutes: JDO TCK Conference Call Friday, Feb 4, 9 am Pacific Time

Posted by Craig L Russell <cr...@oracle.com>.

Attendees: Matthew Adams, Michelle Caisse, Michael Bouschen, Craig
Russell

Agenda:

1.Maven2 upgrade. https://issues.apache.org/jira/browse/JDO-647

There is now a profile to run the tck. To run the tck, run mvn
integration-test. Need to add sub-modules to the parent pom. Upgrade
pom to the latest Derby 10.7.1.1.

It would be good to be able to run the tck on an IUT simply by adding
a profile to the user's settings.xml and not require any changes to
the distributed api, tck, or exectck.

2. Inheritance strategy that results in a table per class... https://issues.apache.org/jira/browse/JDO-674

Seems like proposal 1 doesn't limit what we can do in the future, and
it's a good proposal. AI Craig update the JIRA.

3. Change JPA API dependency to org.eclipse.persistence https://issues.apache.org/jira/browse/JDO-675

There is no official javax.persistence. There is no
org.eclipse.persistence for maven 1. Propose postponing this change
until we leave maven 1. AI Michael update the JIRA.

4. Using Apache parent POM http://www.apache.org/dev/publishing-maven-artifacts.html
, https://issues.apache.org/jira/browse/MPOM

We can start by just adding the Apache parent pom and then the rest
can be added as we work to publish a release.

5. Other issues

Multi-tenancy (cloud) may be a good feature to consider for a future
release. May be similar to openjpa slices?

Use cases as an extension to fetch plan may be a good feature to
consider for a future release. AI Matthew write up a JIRA.

Craig L Russell
Architect, Oracle
http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@oracle.com
P.S. A good JDO? O, Gasp!