John:
I think Castor JDO is a great package, but there is currently
a lack of support being given to it.
I reported a bug in bugzilla 11/11/2002 and have not seen any
progress on it.
Hugh submitted a bug *and* a patch 2/5/2003 and there has been nothing
done with it. I am also hitting the bug that Hugh reported.
>From my standpoint, JDO is unusable in its current form and
nobody seems to be doing anything about it.
At the current time, I am implementing my own alternative
to JDO. I am willing to contribute my time to support JDO,
but I am not going to take on the project myself without
help from the current developers.
Thanks,
Neil.
--
Neil Aggarwal
JAMM Consulting, Inc. (972) 612-6056, http://www.JAMMConsulting.com
Custom Internet Development Websites, Ecommerce, Java, databases
> -----Original Message-----
> From: John McDonald [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, February 18, 2003 4:11 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [castor-dev] Article about Castor-JDO
>
>
> Umm, did I miss something? I'm currently using the castor jdo/xml solution
> for processing over $100 million/month in transactions for some of the
> worlds largest retailers. Our database consists of more than 450
> tables and
> we generate and process more than 250,000 xml documents a month
> using castor
> xml.
>
> It might just be me, but I'd say that these numbers speak to the
> quality of
> the castor project. Someone _please_ prove me wrong. Let me tell
> ya, at this
> point, a great part of the success of my team can be contributed to the
> outstanding workmanship of the castor project.
>
> >> Anyway it has severe basic bugs that are not being worked on.
> Thank you for your opinion. Overall,( and I feel that the numbers stated
> above qualify me to make this statement), castor JDO has seen outstanding
> success and will become a staple in the lives of java engineers
> everywhere.
> I wouldn't bet the farm on unreliable software.
> With _any_ new software venture there are bound to be "bugs" of
> sorts until
> the project has released a major version. I guess that's why the castor
> version is still below '1'. The team is quite humble and will not
> release a
> major version until they feel it's ready. There are a few minor
> issues that
> need to be resolved but, IMHO, the JDO team has contributed to the success
> and ability of our company to integrate partners as quickly as we do. We
> certainly would not move forward, at the current rate of success, without
> it!
>
> -john:m
>
>
> -----Original Message-----
> From: Hugh Winkler [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, February 18, 2003 1:44 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [castor-dev] Article about Castor-JDO
>
>
>
> I think the silence speaks for itself. I don't think JDO is actively
> being maintained? Correct me if I am wrong here somebody. Anyway it has
> severe basic bugs that are not being worked on.
>
> I don't want at all to disparage the Castor team's work. The XML work is
> great. Looks like that's where their efforts currently are focused. I'm
> guessing JDO is not strategic for them right now.
>
> I think it's dangerous though, to leave JDO out there and foster the
> impression that new projects ought to use it. It ought to be labeled
> "experimental" or "deprecated" or something, so that developers don't
> get the wrong impression about its suitability for production systems.
>
>
> Hugh
>
>
>
> -----Original Message-----
> From: Keld Helbig Hansen [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, February 18, 2003 3:43 AM
> To: [EMAIL PROTECTED]
> Subject: [castor-dev] Article about Castor-JDO
>
> I'm currently preparing an article about Castor-JDO for a large Java
> web-site.
> The article is a beginners tutorial to Castor-JDO.
> Since I haven't got practical experience with Castor, I'd like to get in
> contact with a skilled Castor-JDO person that could help me answer some
> technical questions. I've tried to put some of my questions here in the
> newsgroup, but without much success.
> If you're interested in helping me the next week or so I'd be great.
> I'll of course give you due credit in my article.
>
> -----------------------------------------------------------
> If you wish to unsubscribe from this mailing, send mail to
> [EMAIL PROTECTED] with a subject of:
> unsubscribe castor-dev
>
> -----------------------------------------------------------
> If you wish to unsubscribe from this mailing, send mail to
> [EMAIL PROTECTED] with a subject of:
> unsubscribe castor-dev
>
> -----------------------------------------------------------
> If you wish to unsubscribe from this mailing, send mail to
> [EMAIL PROTECTED] with a subject of:
> unsubscribe castor-dev
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
