[jira] Updated: (JDO-202) orm.xsd and unit tests for xsd are missing

[ http://issues.apache.org/jira/browse/JDO-202?page=all ] Craig Russell updated JDO-202: -- Attachment: XSD.patch This patch fixes a syntax error in two of the .xsd files, in which the attributes were defined inside the element instead of outside. > orm.xs

Re: [jira] Commented: (JDO-246) JPOX eliminates duplicates in the query result although DISTINCT is not specified.

Hi! I have more concern about Collection and Map projection: is this query easy to implement? select distinct employees from Department where ... At least I don't know how a SQL datastore could compare the collections one another. So, maybe we should discribe more on Collection and Map

[jira] Commented: (JDO-304) Query failure should print the query that failed in addition to the expected and actual results

[ http://issues.apache.org/jira/browse/JDO-304?page=comments#action_12366040 ] karan singh malhi commented on JDO-304: --- I think if just a couple of calls are being made to these methods then we should simply make changes in the the callers > Query f

[jira] Commented: (JDO-304) Query failure should print the query that failed in addition to the expected and actual results

[ http://issues.apache.org/jira/browse/JDO-304?page=comments#action_12366035 ] Michael Bouschen commented on JDO-304: -- I like the idea of including the JDOQL query string into the error message. The patch QueryTest.patch changes the signature of method

Re: build fails

Yes , thats the one. Thanks On 2/11/06, Michael Bouschen <[EMAIL PROTECTED]> wrote: > > Hi Karan, > > so it is the pm tests causing the additional failure. Please have a look > at the log file which particular test is failing. I assume it is the > ThreadSafe test. If yes this is JDO-238 and Martin

Re: build fails

Hi Karan, so it is the pm tests causing the additional failure. Please have a look at the log file which particular test is failing. I assume it is the ThreadSafe test. If yes this is JDO-238 and Martin is working on fixing the test case. Rehards Michael Hi Michael, derby-app-pm-junit.txt

Re: build fails

Hi Michael, derby-app-pm-junit.txt: ** Tests run: 090, Time: 096 seconds. Failures: 1, Errors: 0 derby-app-query-junit.txt: ** Tests run: 138, Time: 194 seconds. Failures: 2, Errors: 0 derby-app-inheritance3-junit.txt: ** Tests run: 001, Time: 011 seconds. Failures: 0, Errors: 1 derby-

Re: build fails

Hi Karan, which ones fail on your side? My run from last Friday shows the following: derby-app-query-junit.txt: ** Tests run: 138, Time: 185 seconds. Failures: 2, Errors: 0 derby-app-inheritance3-junit.txt: ** Tests run: 001, Time: 009 seconds. Failures: 0, Errors: 1 derby-dsid-query-junit

Re: build fails

Thanks Michelle, I saw the Friday conference call minutes where it was mentioned that 4 tests failed. My build results show that 6 tests failed with 2 errors. On 2/11/06, Michelle Caisse <[EMAIL PROTECTED]> wrote: > > Hi Karan, > > I think that you need to do maven tck20.build from trunk before t

[jira] Updated: (JDO-304) Query failure should print the query that failed in addition to the expected and actual results

[ http://issues.apache.org/jira/browse/JDO-304?page=all ] Craig Russell updated JDO-304: -- Attachment: QueryTest.patch Please review this patch. After applying the patch, failing queries print the query and the expected and actual results. [java] 1) t

[jira] Created: (JDO-304) Query failure should print the query that failed in addition to the expected and actual results

Query failure should print the query that failed in addition to the expected and actual results --- Key: JDO-304 URL: http://issues.apache.org/jira/browse/JDO-304 Project: JDO

[jira] Commented: (JDO-246) JPOX eliminates duplicates in the query result although DISTINCT is not specified.

[ http://issues.apache.org/jira/browse/JDO-246?page=comments#action_12366032 ] Craig Russell commented on JDO-246: --- In case you don't want to bother applying the patch, here are the results with the JPOX jar file as of this morning PST: doRuntck.jdori: O

[jira] Commented: (JDO-246) JPOX eliminates duplicates in the query result although DISTINCT is not specified.

[ http://issues.apache.org/jira/browse/JDO-246?page=comments#action_12366031 ] Michael Bouschen commented on JDO-246: -- The patch VariableInResult.patch looks good! > JPOX eliminates duplicates in the query result although DISTINCT is not > specified.

[jira] Commented: (JDO-303) NPE in ResultSummary if no tests were run

[ http://issues.apache.org/jira/browse/JDO-303?page=comments#action_12366030 ] Michael Bouschen commented on JDO-303: -- Looks good! > NPE in ResultSummary if no tests were run > - > > Key: JDO-303 >

[jira] Updated: (JDO-246) JPOX eliminates duplicates in the query result although DISTINCT is not specified.

[ http://issues.apache.org/jira/browse/JDO-246?page=all ] Craig Russell updated JDO-246: -- Attachment: VariableInResult.patch Please review this patch. It adds two new test queries to the "variables in result" test case. One of the queries projects the vari

[jira] Updated: (JDO-303) NPE in ResultSummary if no tests were run

: [java] No tests were run. [java] See file '/Users/clr/apachejdo/jdo/trunk/tck20/target/logs/20060211-112657/TCK-results.txt' for details. > NPE in ResultSummary if no tests were run > - > > Key: JDO-303 > URL:

[jira] Created: (JDO-303) NPE in ResultSummary if no tests were run

NPE in ResultSummary if no tests were run - Key: JDO-303 URL: http://issues.apache.org/jira/browse/JDO-303 Project: JDO Type: Bug Components: tck20 Versions: JDO 2 beta Reporter: Craig Russell Assigned to: Crai

Re: Issue 158: Specification clarification 11.3

Craig L Russell schrieb: Hi Jörg, I realize that this is not the time to get this resolved. Chapter 16 needs to be updated so it's in line with the 220 work (very similar issues). But we won't finish this in time for JDO2 release this month. Alright, I was afraid so... So we're trying to supp

Re: build fails

Hi Karan, I think that you need to do maven tck20.build from trunk before trying to run the TCK. This will build the required dependencies that maven is complaining about and install them in your local maven repository. -- Michelle Karan Malhi wrote: I checked out a copy of jdo from svn a

build fails

I checked out a copy of jdo from svn and installed maven . After doing the required setup, I ran maven in the tck20. Build fails with the following output: Attempting to download jdo2-api-SNAPSHOT.jar. WARNING: Failed to download jdo2-api-SNAPSHOT.jar. Attempting to download jdo2-enhancer-SNAPSHOT

Re: expected test results

> What do you think? Excellent. Quoting Craig L Russell <[EMAIL PROTECTED]>: > Hi Erik, > > You are right on both. > > Employees 1, 2, and 3 all work on orange, so there should be three > result tuples in both cases. > > I think we might want to make two test cases out of each of these, > making

Re: Issue 158: Specification clarification 11.3

Hi Jörg,I realize that this is not the time to get this resolved. Chapter 16 needs to be updated so it's in line with the 220 work (very similar issues). But we won't finish this in time for JDO2 release this month.So, I'm not proposing to change anything in this area at this time. Let's start disc

Re: Issue 158: Specification clarification 11.3

Hello Craig, the problem is with code that manages PersistenceManagers and transaction demarcation itself, i.e. code without session beans, that is run inside an application server (I can give an example if required). If the semantics of PMF.getPersistenceManager() suddenly change substantial

Release of JSR 243

Javadogs,Here's what I'm looking at for the release of JDO 2. Some of the dates are estimates because they depend on JCP procedures.Feedback is welcome.13-Feb Final specification changes done. Spec sent to Expert Group for final review.20-Feb JPOX RC1 name identified (maven dependency in TCK distri

Re: expected test results

Hi Erik, You are right on both. Employees 1, 2, and 3 all work on orange, so there should be three result tuples in both cases. I think we might want to make two test cases out of each of these, making four tests in total, and remove duplicates in two of the cases by using the distinct k

expected test results

Hi, Some expected results need to be reviewed 1) testNavigation(org.apache.jdo.tck.query.result.VariableInResult) expected: [[1, orange]] got: [[1, orange], [1, orange], [1, orange]] /*UNIQUE*/ null, /*RESULT*/ "p.projid, p.name", /*INTO*/null,