Return-Path: Delivered-To: apmail-db-jdo-dev-archive@www.apache.org Received: (qmail 17774 invoked from network); 21 Feb 2005 16:27:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 21 Feb 2005 16:27:33 -0000 Received: (qmail 14522 invoked by uid 500); 21 Feb 2005 16:27:32 -0000 Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jdo-dev@db.apache.org Delivered-To: mailing list jdo-dev@db.apache.org Received: (qmail 14501 invoked by uid 99); 21 Feb 2005 16:27:32 -0000 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=NO_REAL_NAME,SPF_HELO_PASS X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from smtp.mailix.net (HELO smtp.mailix.net) (216.148.213.132) by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 21 Feb 2005 08:27:29 -0800 Received: from [192.168.8.8] (helo=localhost) by smtp.mailix.net with asmtp (Exim 4.24-H) id 1D3GP7-0006hZ-LS for jdo-dev@db.apache.org; Mon, 21 Feb 2005 08:27:25 -0800 Received: from uu194-7-80-34.unknown.be.uu.net (uu194-7-80-34.unknown.be.uu.net [194.7.80.34]) by webmail.jpox.org (IMP) with HTTP for ; Mon, 21 Feb 2005 08:27:24 -0800 Message-ID: <1109003244.421a0bec59a16@webmail.jpox.org> Date: Mon, 21 Feb 2005 08:27:24 -0800 From: erik@jpox.org To: jdo-dev@db.apache.org References: <003801c51619$e7ff2a20$0100a8c0@jpox> <4219F096.7020506@spree.de> In-Reply-To: <4219F096.7020506@spree.de> MIME-Version: 1.0 User-Agent: Internet Messaging Program (IMP) 3.2.3 X-Originating-IP: 194.7.80.34 X-SA-Exim-Mail-From: erik@jpox.org Subject: Re: Steps to running the TCK against jpox & derby Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Spam-Checker-Version: SpamAssassin 3.0.0 (2004-09-13) on southcarolina.backend X-Spam-Status: No, score=1.4 required=10.0 tests=J_CHICKENPOX_53, J_CHICKENPOX_66,NO_REAL_NAME autolearn=no version=3.0.0 X-Spam-Level: * X-SA-Exim-Version: 3.1 (built Thu Oct 23 13:26:47 PDT 2003) X-SA-Exim-Scanned: Yes X-uvscan-result: clean (1D3GP7-0006hZ-LS) X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Michael, The jdo files should be ok. I will review tonight what's need from JPOX to run the tck. There was a wrong interpretation in JPOX implementation about field modifiers and we have to correct it. Regards, Erik Bengtson Quoting Michael Bouschen : > Hi Erik, > > you mentioned some problem with the metadata below. Is there anything > wrong with the .jdo files? I'm happy to fix any bug in the .jdo files. > > Regards Michael > > > Hi, > > > > Here is the tck11/maven.xml file updated to use the JPOX enhancer. > > > > I still can't run the tck because JPOX has a strictly validation of the > > metadata, and one of these checks needs removal as it was clarified some > > time ago by the EG that it's not needed. > > > > Erik Bengtson > > > > -----Original Message----- > > From: Michelle Caisse [mailto:Michelle.Caisse@Sun.COM] > > Sent: Friday, February 18, 2005 9:52 PM > > To: jdo-dev@db.apache.org > > Subject: Re: Steps to running the TCK against jpox & derby > > > > Michelle Caisse wrote: > > > > > >>Hi, Michael and others, > >> > >>Here's what I've done to get jpox and derby to run against the TCK, to > > > > > >>the point where they need to find tables in the database. > >> > >>1. Put jpox-1.1.0-beta-1.jar in tck11/iut_jars. > > > > > > and put derby.jar and derbytools.jar in tck11/iut_jars > > > > > >>2. Put log4j-1.2.9.jar in tck11/iut_jars. (jpox needed this.) > >>3 Edit tck11/project.properties: > >># iut > >>iut.properties = ${basedir}/jpox.properties > >>4. Create jpox.properties: > >> > > > > javax.jdo.PersistenceManagerFactoryClass=org.jpox.PersistenceManagerFact > > oryImpl > > > >> > > #javax.jdo.PersistenceManagerFactoryClass=org.apache.jdo.impl.fostore.FO > > StorePMF > > > >>org.apache.jdo.ConnectionCreate=true > >> > > > > javax.jdo.option.ConnectionDriverName=org.apache.derby.jdbc.EmbeddedDriv > > er > > > >>javax.jdo.option.ConnectionURL=jdbc:derby:jdotckdb > >>#javax.jdo.option.ConnectionURL=fostore:database/fostore > >>javax.jdo.option.ConnectionUserName=tckuser > >>javax.jdo.option.ConnectionPassword=tckuser > >>javax.jdo.option.Optimistic=false > >>javax.jdo.option.RetainValues=false > >>javax.jdo.option.RestoreValues=false > >>5. In the classpath section of tck11/maven.xml, place these lines > >>BEFORE the JDO jar file lines: > >> > >> > >>else [java] 1) > >> > > > > testGetObjectId(org.apache.jdo.tck.api.jdohelper.GetObjectId)javax.jdo.J > > DOFatalUserException: > > > >>JDO 2.0 capabilities cannot be accessed! Please make sure that you do > >>not have a JDO 1.0 jar in front of the JDO 2 classes in your > > > > CLASSPATH. > > > >> [java] at > >> > > > > org.jpox.AbstractPersistenceManagerFactory.(AbstractPersistenceMan > > agerFactory.java:113) > > > >>6. Manually create a derby database. I'm using iut_jars as the derby > >>system directory, meaning that it looks there for databases and > >>derby.properties. I wrote some scripts to create the db. The > >>procedure for deleting a derby database is an OS delete operation on > >>the directory and files. > >>7. Add the following line to maven.xml in the >>name="runtck.single" ...> section: > >> >>value="${basedir}/iut_jars"/> > >> > >>-- Michelle > >> > > > > > > > > ------------------------------------------------------------------------ > > > > > > > > > > > xmlns:j="jelly:core" > > xmlns:ant="jelly:ant" > > xmlns:maven="jelly:maven" > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Run all tck tests from testlist ${jdo.testlist} > > > classname="${jdo.testrunnerclass}"> > > > > > > value="${jdo.resultprinterclass}"/> > > > > > > value="${basedir}/jdori2.properties"/> > > > > > > > > > > > > > > > > Run tck test org.apache.jdo.tck.${test} > > > classname="org.apache.jdo.tck.${test}"> > > > > value="${jdo.resultprinterclass}"/> > > > > > > value="${basedir}/jdori2.properties"/> > > > > > > > > > > > > > > > > > > > > > message="Metadata directory does not exists, please use goals > useapplicationdirectory or usedatastoredirectory to setup the metadata."/> > > > > > includes="${jdo.pcclasses.files} > ${jdo.paclasses.files}"/> > > > includes="**/*.jdo **/*jdoTest.properties"/> > > > > > > > > > > > > > > > > Run enhancer > > > classname="${enhancer.main}" > > classpathref="project.class.path"> > > > > > > > > > > > > > > > > Run JDORI enhancer > > > classname="${jdo.enhancer.main}" > > classpath="${jdo.enhancer.classpath}"> > > > > > > > > > > > > > > > > > > includes="**/*.jd*"/> > > refid="jdo.files"/> > > > > > > > > > failonerror="true" > > fork="true"> > > > > > > > > > > > > Classes are now JDO-enhanced for JPOX test scenario > "${maven.jpoxtest.name}" > > > > > > > > > > > > > > > > > > > > > includes="**/*.jdo, **/*jdoTest.properties"/> > > > > > > > includes="**/*jdoTest.properties.d"/> > > to="*jdoTest.properties" /> > > > > > > > > > > > > > > > > > > > > > > > includes="**/*.jdo, **/*jdoTest.properties"/> > > > > > > > includes="**/*jdoTest.properties.a"/> > > to="*jdoTest.properties"/> > > > > > > > > > > > > > > > > > > > > > includes="**/*.jdo, **/*jdoTest.properties"/> > > > > > > > includes="**/*jdoTest.properties.d"/> > > to="*jdoTest.properties" /> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > value="org.apache.jdo.tck.util.SwingTestRunner"> > > > > > > > value="org.apache.jdo.tck.util.BatchTestRunner"> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > 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 >