Return-Path: Delivered-To: apmail-db-jdo-dev-archive@www.apache.org Received: (qmail 19284 invoked from network); 10 Mar 2005 16:03:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 10 Mar 2005 16:03:46 -0000 Received: (qmail 54966 invoked by uid 500); 10 Mar 2005 16:03:42 -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 54871 invoked by uid 99); 10 Mar 2005 16:03:42 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from mail.spree.de (HELO miraculix.spree.de) (62.154.194.149) by apache.org (qpsmtpd/0.28) with ESMTP; Thu, 10 Mar 2005 08:03:40 -0800 Received: from [127.0.0.1] (merlin.spree.de [172.16.1.107]) by miraculix.spree.de (8.11.6/8.11.6) with ESMTP id j2AG3XO27040 for ; Thu, 10 Mar 2005 17:03:33 +0100 Message-ID: <42306FD5.8050801@spree.de> Date: Thu, 10 Mar 2005 17:03:33 +0100 From: Michael Bouschen Organization: Tech@Spree Engineering User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: jdo-dev@db.apache.org Subject: Re: referencing jdo 2 dtd References: <422F9F97.5020209@sun.com> In-Reply-To: <422F9F97.5020209@sun.com> Content-Type: multipart/mixed; boundary="------------070407060707050203060701" X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N --------------070407060707050203060701 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hi Michelle, > Michael et al., > > I created an orm directory parallel to the new applicationidentity and > datastoreidentity directories. I propose to have the orm directory parallel to jdo: tck11/test/conf /java /jdo /orm Then the directory jdo includes JDO metadata stored in .jdo files, where the directory orm is for mapping metadata. What do you think? > To run tests with mapping, I will have > to edit all of the metadata files to reference a 2.0 dtd. > Unfortunately, this is a hack until we can actually put the content in > the repository and create a tck 2.0 directory in which we can make this > a permanent feature of the metadata files. Yes this is an issue. Attached you find a small script changeDoctype.sh that allows you to change the metadata files (rather than doing this manually). It takes a list of file names as command line arguments. In each file it replaces a line starting with ' I used the 1.0 doctype as an example. The script save the original file with the suffix .orig. It prints out the name of the file it is currently processing. You might need to change the permissions of the file, before you can execute it: chmod 777 changeDoctype.sh. The following line finds the .jdo file under the current directory and runs the script: find . -name '*.jdo' | xargs changeDoctype.sh This is a hack too, but less work compared to the manual change. Regards Michael > > -- Michelle -- 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 --------------070407060707050203060701 Content-Type: text/plain; name="changeDoctype.sh" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="changeDoctype.sh" NEWDOCTYPE='' for i in $* do echo $i cp $i $i.orig sed "/^ $i done --------------070407060707050203060701--