One other thing I forgot to mention last night...
Just in the last two weeks there was some discussion among the
members of the local Java User's Group. A few people were complaining
about how difficult and frustrating it was using Hibernate, due to
some of its limitations. They were
The fact that JPA has not really had much impact (that is the
perception out there, I don't know the reality, but in the market it
is perception that matters) does give JDO a new opportunity to rise
up and be reconsidered.
This is very important point, but maybe optimistic. I would say
[ http://issues.apache.org/jira/browse/JDO-345?page=all ]
Michael Bouschen resolved JDO-345.
--
Resolution: Fixed
Cleaned up the imports and checked in the patch into the trunk and into branch
2.0.1 (see revision 453263).
[ http://issues.apache.org/jira/browse/JDO-417?page=all ]
Craig Russell updated JDO-417:
--
Attachment: JDO-417.patch
Please review this patch.
I've anticipated the release that this will be shipped with, 2.1.
I've removed references to import of the xa
Hi All,
It's been a while since I've posted. I've taken down the JDOMax website, and
I'm now focusing my efforts on Shades.
http://sourceforge.net/projects/shadesdb
I continue to think that JDO is a leap forward, and I continue to share my
great experiences as both a user of JDO and an
What about trying to work with the OpenJPA
(http://incubator.apache.org/openjpa/) team to develop an integration
strategy? After all, both projects are at the ASF and there is no harm
in discussing it.
Bruce
--
perl -e 'print unpack(u30,D0G)[EMAIL
PROTECTED]5R\F)R=6-E+G-N61ED\!G;6%I;\YC;VT*
);'
[
http://issues.apache.org/jira/browse/JDO-430?page=comments#action_12440199 ]
Michelle Caisse commented on JDO-430:
-
In this test case order information will be contained in a database column
only, not in a field of the class.
JPOX fails
[ http://issues.apache.org/jira/browse/JDO-421?page=all ]
Michelle Caisse resolved JDO-421.
-
Resolution: Fixed
Fixed with revision: 453315
Verified that with the current JPOX, these patches, and JDK 1.5, there are no
error messages in the enhancer
[ http://issues.apache.org/jira/browse/JDO-193?page=all ]
Michelle Caisse resolved JDO-193.
-
Resolution: Fixed
JDO-430 is now tracking the remaining issues on this case.
Need new test cases for Map and List where there is no join table; the key is
a
[
http://issues.apache.org/jira/browse/JDO-430?page=comments#action_12440262 ]
Michelle Caisse commented on JDO-430:
-
I checked in changes to the .orm and .sql files (revision: 453382). There are
two issues:
(1) When using the mapped-by
[ http://issues.apache.org/jira/browse/JDO-430?page=all ]
Michelle Caisse reassigned JDO-430:
---
Assignee: Andy Jefferson (was: Michelle Caisse)
JPOX fails new test CompletenessTestList, configuration companyListWithoutJoin
[ http://issues.apache.org/jira/browse/JDO-373?page=all ]
Michelle Caisse resolved JDO-373.
-
Resolution: Fixed
revision: 453390
Comment error in OptimisticFailure
--
Key: JDO-373
I am not at all opposed to what Andy has suggested. I guess the big
question is whether JDO offers enough beyond JPA that makes this
effort worthwhile, versus everyone just doing JPA.
On Oct 5, 2006, at 7:17 PM, Ilan Kirsh wrote:
My personal feeling after reading the JPA spec and two
I found now an interesting poll at http://www.java.net/pub/pq/122. The
results should be taken suspiciously of course, but it seems that JDO still
has some hope as it is. However, probably by extending JPA as Hibernate and
TopLink do it has much better chances. I agree that the big question is
Hi,
We will have our regular meeting Friday, October 6 at 9 am PDT to
discuss JDO TCK issues and status.
Dial-in numbers are:
866 230-6968 294-0479#
International: +1 865 544-7856
Agenda:
1. Test challenge issues and status
2. Reflection based implementations
3. JDOQL subquery
15 matches
Mail list logo
