This one time, at band camp, Krzysztof Swietlinski said:
KS>One thing you have to remember when looking into using
KS>castor for db access is that there is almost no work
KS>going on. There are well known bugs that nobody even
KS>plans to fix. There are serious performance issues for
KS>any but trivial schema.
KS>Documentation (both separate and source code comments)
KS>is non existent. Also look how many JDO related
KS>questions go unanswered.
KS>We did use castor for real world project and I think
KS>it was a mistake.
KS>
KS>If you want to use open source persistance framework
KS>you should look rather at OJB:
KS>http://jakarta.apache.org/ojb/
KS>It's active, it's well documented and it's moving
KS>forward incredibly fast.
Krzysztof, All,
The Castor JDO source has been minimally active for far too long now. The
trouble has been lack of contribution from the community. There are really
only two active developers, myself and Ned Wolpert - and Ned's wife just
had baby a couple of weeks ago so he'll be out of the loop for a while.
Due to this lack of community contribution, I have really been handling
almost everything for the last few months now. Let me tell you, the
workload is far too much for one person to handle. What is sorely needed
is community involvement. This includes fixing bugs, updating docs,
adding features, etc. I became a committer on the project because of my
contributions to the maillist, patches, docs, etc.
I want to see Castor move forward, but I cannot do it alone. If you
are interested in becoming involved with Castor JDO and furthering its
feature set, please start to contribute. If you have any questions about
how you can contribute, please post them to the list and let's discuss
them for all to see.
Bruce
--
perl -e 'print unpack("u30","<0G)U8V4\@4VYY9&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");'
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
