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 issues
>> 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
Carlos Sanchez wrote:
On 1/2/07, Rahul Thakur <[EMAIL PROTECTED]> wrote:
- Original Message -
From: "Brett Porter" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, January 03, 2007 4:59 PM
Subject: Re: [discuss] iBatis, JPA and Java 5.0
> I've been thinking stay
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 gi
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
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
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 gav
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.
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 plugg
