Hi,
I'm currently in the throes of replacing my in-house persistence layer with
JDO2, and I was wondering whether anyone out there can recommend a specific
open source JDO implementation.
I've been testing with one such implementation for the past couple of weeks,
but it seems to have problems with tracking detached object versions for
optimistic updates. I guess I could trawl through the code and fix it, and
live with forked code while hoping the changes are accepted etc., but I
can't afford to spend too much time on it. So I've decided to put it aside
and try out other JDO2 implementations -- so I'd appreciate any
recommendations.
If all else fails I may even try a (gasp) commercial implementation -- but
there again, how can I be sure it will be a good implementation, and how
quickly will bugs be fixed?
TIA,
Michael
Luke Webber - 21 Sep 2005 13:50 GMT
Are you also considering replacing your DVDs with VHS tapes? JDO is
dead. I advise you to consider Hibernate Annotations instead.
Luke
> Hi,
>
[quoted text clipped - 16 lines]
> TIA,
> Michael
MikL - 21 Sep 2005 14:23 GMT
> I advise you to consider Hibernate Annotations instead.
Why?
MikL - 23 Sep 2005 10:48 GMT
>> I advise you to consider Hibernate Annotations instead.
>
> Why?
I'm serious -- I'm interested in why you recommend it.
Luke Webber - 25 Sep 2005 23:44 GMT
>>> I advise you to consider Hibernate Annotations instead.
>>
>>Why?
>
> I'm serious -- I'm interested in why you recommend it.
I thought I answered this. Did you miss my reply?
I recommended Hibernate because it seems far more popular than JDO. JDO
is much disregarded these days, but Hibernate has a thriving user base.
OTOH, I don't much like all the XML configuration files required by the
standard Hibernate, hence Hibernate Annotations. I've not yet used it in
a major project, but I've read the standard text and had a play, and
it's very impressive.
Luke