Dear Bruce,
 
Thanks for the fast reply, and I appreaciate your kindness and patience on all the questions from me.
 
I think this is the late message from me on Castor's preference and its prospect. I am sorry for asking these non-technical questions.
 
My last question sounds as: How do you think Hibernate (Hibernate.org) and its capability in solving the same problem.  Do you think that Hibernate is a threat to Castor? 
 
Thank you.
 
Cheers,
Ng Keng Yap 
 
-------Original Message-------
 
Date: Thursday, October 07, 2004 04:10:08
Subject: Re: [castor-user] DLL Generation from OR Mapping in Castor possible without XDoclet?
 
This one time, at band camp, Ng Keng Yap said:
 
NKY>I am glad that castor has such a complete solution for transformation from XML to RDBMS (XML-Data Binding). I just wonder why not Castor adheres to Sun's JDO spec
NKY>for its object persistence for higher compatiblity. Do you mind what is the reason behind it?
 
Adherence to the Sun JDO spec was never the goal of the Castor
Project. This is due mainly to the fact that the JDO spec came out
only after Castor was already available. Instead, Castor's goal was
to adhere more closely to the EJB spec's Container Managed Persistence.
 
I would really like to offer a JDO 2.0 compliant implementation of
Castor for the Castor 2.0. But I really don't know what will happen
with the JDO spec since the joint effort between the JDO and EJB
JSRs have joined efforts. Also Castor 2.0 is only a twinkle in our
eyes right now. Only time will tell.
 
Bruce
--
perl -e 'print unpack("u30","<0G)[EMAIL PROTECTED]&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");'
 
The Castor Project
 
Apache Geronimo
 
 
 
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
         unsubscribe castor-user
----------------------------------------------------------- 
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
        unsubscribe castor-user

Reply via email to