Hi Michael,
> The test case defines a superclass and a subclass. Both are persistence
> capable and both define define persistent fields. Mistakenly, I assigned
> all column/field mappings to the subclass in the orm metadata. That's
> why the exception is thrown.
> If I move the fields in the supe
Hi Andy,
I figured out that the exception below was thrown because I made a
mistake in the orm metadata:
The test case defines a superclass and a subclass. Both are persistence
capable and both define define persistent fields. Mistakenly, I assigned
all column/field mappings to the subclass
Hi,I think there is a misunderstanding, and we need to update the wiki page to be more clear.We now have the ability to run a single test case in multiple combinations of:databaseidentity type (application or datastore)test case classThis is only slightly different from the former runtck.jdorisingl
Hi Andy,
Hi Michael,
I think, we do not support this case currently. You can run a single
test class, but you cannot run a single test case if the test class has
several test cases like class "NewObjectIdInstance".
OK. I consider it a "must-have". We used to have "runsingle" or something.
Hi Michael,
> I think, we do not support this case currently. You can run a single
> test class, but you cannot run a single test case if the test class has
> several test cases like class "NewObjectIdInstance".
OK. I consider it a "must-have". We used to have "runsingle" or something. I
see no
Hi Andy,
This is a configuration file
executing only test cases of class "NewObjectIdInstance". You may adapt
the entry "jdo.tck.classes" as appropriate. Please copy this file to
".../tck20/conf", then execute in tck20:
Yes, but how do I run a single test ?
I'm not interested in running a bl
> This is a configuration file
> executing only test cases of class "NewObjectIdInstance". You may adapt
> the entry "jdo.tck.classes" as appropriate. Please copy this file to
> ".../tck20/conf", then execute in tck20:
Yes, but how do I run a single test ?
I'm not interested in running a block of
Hi Andy,
I attached a file (sometests.conf). This is a configuration file
executing only test cases of class "NewObjectIdInstance". You may adapt
the entry "jdo.tck.classes" as appropriate. Please copy this file to
".../tck20/conf", then execute in tck20:
maven -o -Djdo.tck.cfglist=sometests
> I sent a patch (Assertion-A7-A8.patch) containg the test case
> (NewObjectIdInstance.java) to jdo-dev today. I ran it with JPOX build
> "20050628.022915". This seems to be the latest build available under
> nightly builds. I still get the exception (see below).
>
> Please have a look at the test
Hi Andy,
I sent a patch (Assertion-A7-A8.patch) containg the test case
(NewObjectIdInstance.java) to jdo-dev today. I ran it with JPOX build
"20050628.022915". This seems to be the latest build available under
nightly builds. I still get the exception (see below).
Please have a look at the t
> I have written a test case checking single field identity. For this
> purpose, I created new PC classes, new jdo files, new orm files, and I
> extended the schema for application identity. When I run the test case,
> I get a JDOFatalInternalException from JPOX (see below). Currently, I
> run buil
Hi Erik, Andy,
I have written a test case checking single field identity. For this
purpose, I created new PC classes, new jdo files, new orm files, and I
extended the schema for application identity. When I run the test case,
I get a JDOFatalInternalException from JPOX (see below). Currently,
12 matches
Mail list logo
