I have been using Castor for a while now.  Initially I choose Castor over OJB simply because of its XML support.  However, I am again evaluating OJB as a replacement for Castor because we have done nothing with Castor-XML to date. 
 
In terms of RDBMS persistence capibilities, in my opinion, OJB has an edge over Castor.  It is already ODMG compliant, and work is already under way for a JDO compliant interface (and XML data binding is planned).  So as a "pro", my guess is that OJB will be the first open source project with a JDO-compliant implementation.
 
If you absolutely need XML data binding capability, Castor is the only choice (between these two) for now.  Although another thought I am planning on researching is mapping persistence using OJB and mapping XML binding using Castor on the same objects simultaneously (although this would lead to having to maintain two seperate sets of mapping files).
 
HTH
 
 

********************************************
Steve Ebersole
IT Integration Engineer
Vignette Corporation
512.741.4195

Visit http://www.vignette.com

********************************************

-----Original Message-----
From: Jan Agermose [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 23, 2002 5:32 AM
To: [EMAIL PROTECTED]
Subject: Re: [castor-dev] JDO Performance Issue ... Again

sorry if this is off topic.

If you know objectbridge and castor, could you tell me what made you go for castor over objectbridge? We are in the process of "evaluating" different implementations so any comments on pro and cons on castor/objectbridge/others would be much appreciated.

Do someone know of a site that has compared some of the different implementations Castor/jdo/odmg?

Jan Agermose


On Mon, 2002-04-22 at 17:01, Christoph Kiehl wrote:
Hi Jan,

>> Otherwise refactoring this collection handling part would be definitly
>> an improvement ...
>
> It's not only an improvement it is a requirement!!
> If this doesn't get fixed castor JDO is completely
> useless for any projects with anything but the simplest
> class hierachies.

We didn't experienced performance problems yet, perhaps because we don't
have more than one or two collections in a class and if more, these
collections have a very small size (less than 10 elements or even empty).

I think there is no active development on the JDO part currently. Perhaps
someone from exolab could give a comment on this?

An alternative would perhaps be: http://objectbridge.sourceforge.net/

These project seems to be more active.

Regards
Christoph

----------------------------------------------------------- 
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
	unsubscribe castor-dev


Reply via email to