JDO is not bad, but JPOX has proven to be less then robust.
Sometime ago I joined this list to provide an easier a communication channel
for solving continuum/jpox issues and besides a few emails no one has ever
requested any help on issues neither gave any feedback.
JPOX is the only
well, I believe a lot of the 'less then robust' stem from a couple of
things we ran into last summer doing some related work. (at least for
me, others may vary)
I know joakim talked to erik some about the issues we ran into with
plexus-security at the time (now plexus-redback).
For those
Carlos Sanchez wrote:
On 1/2/07, Rahul Thakur [EMAIL PROTECTED] wrote:
- Original Message -
From: Brett Porter [EMAIL PROTECTED]
To: continuum-dev@maven.apache.org
Sent: Wednesday, January 03, 2007 4:59 PM
Subject: Re: [discuss] iBatis, JPA and Java 5.0
I've been thinking stay
- Original Message -
From: Rahul Thakur [EMAIL PROTECTED]
To: continuum-dev@maven.apache.org
Sent: Monday, January 08, 2007 4:05 PM
Subject: Re: [discuss] iBatis, JPA and Java 5.0
snip
Having said all of that, my vote (which no one need care about, since
I haven't had much time
On 1/2/07, Rahul Thakur [EMAIL PROTECTED] wrote:
- Original Message -
From: Brett Porter [EMAIL PROTECTED]
To: continuum-dev@maven.apache.org
Sent: Wednesday, January 03, 2007 4:59 PM
Subject: Re: [discuss] iBatis, JPA and Java 5.0
I've been thinking stay with JDO for now, look at JPA
snip
Having said all of that, my vote (which no one need care about, since
I haven't had much time to actually contribute code here) is to
support hibernate with slight abstraction on top of it (modeled on
JPA's entity manager), so we get the benefits of transparent
persistence without
Quoting Jason van Zyl [EMAIL PROTECTED]:
JDO is not bad, but JPOX has proven to be less then robust.
Sometime ago I joined this list to provide an easier a communication channel for
solving continuum/jpox issues and besides a few emails no one has ever
requested any help on issues neither gave
its not just jpox in continuum but also the jpox usage in the
plexus-security rbac and user management stores that joakim worked
through a couple of months back while consulting with you I think.
Joakim can explain more on that if he likes. I just remember that we
had a mess of issues in getting
Hi Erik,
I am playing around refactoring some store stuff using jdo and ibatis on
a separate branch (key-refactoring) and welcome any help i can get with
JDO :-). I am usually on #continuum on IRC (irc.codehaus.org), or happy
to join jpox lists.
Cheers,
Rahul
Erik Bengtson wrote:
Quoting
On 03/01/2007, at 4:29 PM, Rahul Thakur wrote:
I am not sure what you refer to by:
[snip]
The way Continuum is designed means
you get to a certain point where you want to save an object and
you find that you can't, or you aren't saving everything you want,
etc.
[/snip]
Could you please
Yeah. But to have truly pluggable persistence, then we end up having to
pick LCD features. For isntance, if we want JDO, iBatis, and
JPA/Hibernate as possible approaches, then our design has to pretty much
ignore transparent relationship manifestation that JPA/hibernate/Toplink
provide.
Sorry, I was writing my post when this came in. I'm in general
agreement, and while I do think moving to something more than JDO is
important, Brett is right, the use of hte store could use a good audit
and re-factor. Probably some of the problems of strange access
approaches used currently
On 2 Jan 07, at 10:59 PM 2 Jan 07, Brett Porter wrote:
I've been thinking stay with JDO for now, look at JPA in the long
term.
I think anyone who wanted to look at an iBatis store I say go for it.
JDO is not bad, but JPOX has proven to be less then robust. If we
were using Kodo it
These buzzwords have been making rounds on IRC and dev list :-), and
after slight digging around I found a reference to a similar discussion
here:
http://www.mail-archive.com/ibatis-user-java@incubator.apache.org/msg01251.html
Agreed that the store implementation for Continuum should be
I've been thinking stay with JDO for now, look at JPA in the long term.
I haven't used iBatis, and would be happy to hear some practical
experience from people who have. I tend to think of it as a more
productive JDBC, as opposed to the different programming model of
JDO/Hibernate/JPA.
15 matches
Mail list logo
