Another thought... If you use something like JPA and Hibernate you can allow users to setup the client with their favorite DB through a simple configuration file. You can ship it with *(insert Java embeddable DB here) as the default but allow the open source community to run it on something else if they want. This would also open the DB to be queried from other platforms. For example I could run the Java client on MySQL and then use Perl to write my own cool queries directly on the DB. (There may be a good solution to your GEDCOM import problem here as well... or integration with other platforms and programs who do not intend to adopt the web service API)
--John From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Finlay Sent: Tuesday, May 15, 2007 9:53 AM To: LDS Open Source Software Subject: RE: [Ldsoss] Database for FamilySearch OpenSource Client I've used Derby and HSQL. Both are good embeddable DBs. It sounds like H2 is worth looking into though. For a database abstraction framework, I would go with the new standard Java Persistence API (JPA). With the JPA and Java 5's annotations and generics, developing a persistence layer is a breeze. See http://java.sun.com/javaee/technologies/persistence.jsp and http://java.sun.com/javaee/overview/faq/persistence.jsp Here is a good tutorial using Netbeans and Derby https://glassfish.dev.java.net/javaee5/persistence/persistence-example.h tml The JPA also runs on top of an implementation like Hibernate or TopLink. So you not only get the advantage of coding to an open standard, but you also get the power and stability of hibernate. --John John Finlay Instructor - Neumont University <http://www.neumont.edu/> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gordon Clarke Sent: Friday, June 15, 2007 8:51 AM To: LDSOSS@LISTS.LDSOSS.ORG Subject: [Ldsoss] Database for FamilySearch OpenSource Client LDS Developers, I have three important questions about the Java-based Open Source Desktop Client that FamilySearch is developing to work in conjunction with our New FamilySearch master family tree. All answers and any comments about the database issue will be greatly appreciated. 1) What open source database would you recommend? 2) Do you know of a type of architecture that could be used to create a framework extensible for different databases? 3) What do you think about the Derby? H2? Thanks so much, Gordon Clarke FamilySearch DevNet Manager ________________________________ NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
_______________________________________________ Ldsoss mailing list Ldsoss@lists.ldsoss.org http://lists.ldsoss.org/mailman/listinfo/ldsoss
