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 things working there because of something like certain lists of objects where not supported or something of that ilk. We need to go back through and refactor some of the fields on the models and we're kinda dreading having to do it since we'll have to deal with the store again.
jesse On 1/3/07, Erik Bengtson <[EMAIL PROTECTED]> wrote:
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 any feedback. JPOX is the only implementation that passes JDO 2 TCK, and less than robust argument does not sounds fair since you dont even ask for help. Regards, Erik Bengtson
-- jesse mcconnell [EMAIL PROTECTED]
