TestHashMapStringKeyCollections.test : schema incorrect
---
Key: JDO-260
URL: http://issues.apache.org/jira/browse/JDO-260
Project: JDO
Type: Bug
Components: tck20
Reporter: Andy Jefferson
Assigned to:
TestHashSetCollections, TestSetCollections : schema incorrect
-
Key: JDO-261
URL: http://issues.apache.org/jira/browse/JDO-261
Project: JDO
Type: Bug
Components: tck20
Reporter: Andy Jefferson
Hi,
does the TCK currently include any tests for managed environments?
Thanks for information,
Jörg
--
__
Dipl.-Inf. Jörg von Frantzius |artnology GmbH
|Milastr. 4
Tel +49 (0)30
No.
Quoting Jörg von Frantzius [EMAIL PROTECTED]:
Hi,
does the TCK currently include any tests for managed environments?
Thanks for information,
Jörg
--
__
Dipl.-Inf. Jörg von Frantzius |artnology GmbH
Hi Jörg,
Hi,
does the TCK currently include any tests for managed environments?
not that I'm aware of.
Regards Michael
Thanks for information,
Jörg
--
Michael Bouschen[EMAIL PROTECTED] Engineering GmbH
mailto:[EMAIL PROTECTED]http://www.tech.spree.de/
[
http://issues.apache.org/jira/browse/JDO-256?page=comments#action_12360294 ]
Andy Jefferson commented on JDO-256:
Any chance of a clue as to what data has changed ? Something to do with
medical and dental insurance ? Wading through this object model
I found one project that may be interesting. It is called Jencks (David Jencks),
and apache licensed.
There are some samples of it in combination of Spring. Could the TCK incorporate
JCA adapter tests if technically feasible?
Regards,
Quoting [EMAIL PROTECTED]:
To automate a JCA adapter test
[ http://issues.apache.org/jira/browse/JDO-239?page=all ]
Andy Jefferson reassigned JDO-239:
--
Assign To: Andy Jefferson (was: Erik Bengtson)
JPOX throws NPE when result class is specified with no result clause for
deletion by query using single
[ http://issues.apache.org/jira/browse/JDO-239?page=all ]
Andy Jefferson resolved JDO-239:
Resolution: Fixed
Fixed in JPOX CVS. Builds from 14/12/2005 will have this.
JPOX throws NPE when result class is specified with no result clause for
[
http://issues.apache.org/jira/browse/JDO-243?page=comments#action_12360312 ]
Andy Jefferson commented on JDO-243:
Why ? Is it not allowed for the JDO implementation to interpret that fields in
the result should be automatically added to the grouping
[
http://issues.apache.org/jira/browse/JDO-243?page=comments#action_12360314 ]
Michael Bouschen commented on JDO-243:
--
my $0.02:
I think it is dangerous to automatically add the field to the grouping, because
this changes the semantics of the query as
[
http://issues.apache.org/jira/browse/JDO-256?page=comments#action_12360316 ]
Michael Bouschen commented on JDO-256:
--
Both xml files companyNoRelationships and companyAllRelationships define the
same pc instances, but companyNoRelationships does not
Since Apache JDO is no longer in this incubator thing, does this mean that
the following is still valid for checking out ?
svn checkout http://svn.apache.org/repos/asf/incubator/jdo
Just that I get (and have for the last 5 hours), some silly response about
unable to contact svn.apache.org.
7. Fieldtypes test status (Michelle) Everything working except
TestArrayCollections. JIRA issue is filed against JPOX.
Really ?
I check out latest SVN and with latest JPOX I get errors in
TestHashSetCollections, TestSetCollections, TestHashMapStringKeyCollections
and have for some time. I
Hi Andy,
Since Apache JDO is no longer in this incubator thing, does this mean that
the following is still valid for checking out ?
svn checkout http://svn.apache.org/repos/asf/incubator/jdo
good question! I'm still using the above url. But you are right this
might change as part of JDO
Hi,What will happen is that at some point soon, the repository will be changed, leaving the old repository in place.When this happens, we will publicize it and hopefully lock the incubator repo so that no more checkins will be done to the incubator alias. The idea is that we will do an svn cp from
[
http://issues.apache.org/jira/browse/JDO-243?page=comments#action_12360385 ]
Craig Russell commented on JDO-243:
---
Here's the specification:
When grouping is specified, each result expression must be one of:
an expression contained in the grouping
17 matches
Mail list logo