  | Mailing List | | Home | | Forum Home | | JBoss - Java Application Server | | Tomcat - JSP/Servlet container | | Struts - A MVC web framework | | iText - An open source PDF Java Library | | JDOM - JDOM XML Parser | | JSP - A mailing list about Java Server Pages specification and reference | | J2EE - A mailing list for Java(tm) 2 Platform, Enterprise Edition | | J2EE Pattern - An interest list for Sun Java Center J2EE Pattern Catalog | | Servlet - A mailing list for discussion about Sun Microsystem's Java Servlet API Technology | |
Struts & Hibernate
|
|
|
  | | | Concept for modeling hierarchical data | Concept for modeling hierarchical data 2005-12-19 - By Taylor, Kevin
Back If you want an OO db that is very lightweight, try: http://www.prevayler.org.
> Kevin Taylor > > -- --Original Message-- -- > From: A mailing list for Java(tm) 2 Platform, Enterprise Edition [SMTP:J2EE -INTEREST@(protected)] On Behalf Of Florian Lindner > Sent: Thursday, December 15, 2005 2:11 PM > To: J2EE-INTEREST@(protected) > Subject: Re: Concept for modeling hierarchical data > > Am Dienstag, 13. Dezember 2005 21:31 schrieb Dharmendra Sharan: > > Hi Florian, > > > > I haven't used Object Oriented databases as such, but have mostly come > > across Relational Databases which seem to be the mainstream approach, and > > works for most cases. > > > > In case you feel there's a strong reason that the application's usage > > profile would rely and "heavily" use the hierachical relationship, then > > you'd need to check whether it makes more sense to store your Java objects > > natively in an OO datbase as opposed to serializing them in XML and storing > > them in an XML database and work in that manner. Here are some vendor names > > for the same: > > > > a. Object Oriented data model > > - Excelon/Object Design (optimized for OO storage/rerieval) > > This DB is WAY to expensive. My projekt in non-commercial/non-profit so I must > rely on freeware/OSS software. Same of Tamino. > > > > > b. XML based data model > > - Tamino (optimized for XML storage/retrieval) > > - Xindice (optimized for XML storage/retrieval) > > Xindice is optimized for storing a large number of smaller XML documents. > AFAIK these document itself are not organized hierarchily. Please correct if > I am wrong. > > > - Excelon/Object Design > > > > c. Relational data model (optimized for Relational storage/retrieval) > > - Oracle > > - Sybase > > - SQL Server > > - MySQL (opensource!) > > That will probably be the way to go (at least at the beginning.) > > > - DB2 > > Thanks for comment, > > Florian > > =========================================================================== > To unsubscribe, send email to listserv@(protected) and include in the body > of the message "signoff J2EE-INTEREST". For general help, send email to > listserv@(protected) and include in the body of the message "help".
=========================================================================== To unsubscribe, send email to listserv@(protected) and include in the body of the message "signoff J2EE-INTEREST". For general help, send email to listserv@(protected) and include in the body of the message "help".
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <TITLE>RE: Concept for modeling hierarchical data</TITLE> </HEAD> <BODY> <!-- Converted from text/rtf format -->
<P><SPAN LANG="en-us"><FONT COLOR="#0000FF" SIZE=2 FACE="Arial">If you want an OO db that is very lightweight, try: <A HREF="http://www.prevayler.org">http:/ /www.prevayler.org</A>.</FONT></SPAN> </P>
<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Tahoma">Kevin Taylor</FONT></SPAN> </P> <UL> <P><SPAN LANG="en-us"><FONT SIZE=1 FACE="Arial">-- --Original Message-- --< /FONT></SPAN>
<BR><SPAN LANG="en-us"><B><FONT SIZE=1 FACE="Arial">From: </FONT></B > <FONT SIZE=1 FACE="Arial">A mailing list for Java(tm) 2 Platform, Enterprise Edition [SMTP:J2EE-INTEREST@(protected)]</FONT><B> <FONT SIZE=1 FACE="Arial" >On Behalf Of</FONT></B><FONT SIZE=1 FACE="Arial"> Florian Lindner</FONT></SPAN> </P>
<P><SPAN LANG="en-us"><B><FONT SIZE=1 FACE="Arial">Sent: </FONT></B> <FONT SIZE=1 FACE="Arial">Thursday, December 15, 2005 2:11 PM</FONT></SPAN>
<BR><SPAN LANG="en-us"><B><FONT SIZE=1 FACE="Arial">To: </FONT></B> <FONT SIZE=1 FACE="Arial">J2EE-INTEREST@(protected)</FONT></SPAN>
<BR><SPAN LANG="en-us"><B><FONT SIZE=1 FACE="Arial">Subject: </FONT></B> <FONT SIZE=1 FACE="Arial">Re: Concept for modeling hierarchical data</FONT></SPAN> </P>
<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">Am Dienstag, 13. Dezember 2005 21:31 schrieb Dharmendra Sharan:</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">> Hi Florian,</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">></FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">> I haven 't used Object Oriented databases as such, but have mostly come</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">> across Relational Databases which seem to be the mainstream approach, and</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">> works for most cases.< /FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">></FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">> In case you feel there's a strong reason that the application's usage</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">> profile would rely and "heavily" use the hierachical relationship, then</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">> you'd need to check whether it makes more sense to store your Java objects</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">> natively in an OO datbase as opposed to serializing them in XML and storing</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">> them in an XML database and work in that manner. Here are some vendor names</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">> for the same:</FONT>< /SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">></FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">> a. Object Oriented data model</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">> - Excelon/Object Design (optimized for OO storage/rerieval)</FONT></SPAN> </P>
<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">This DB is WAY to expensive. My projekt in non-commercial/non-profit so I must</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">rely on freeware/OSS software. Same of Tamino.</FONT></SPAN> </P>
<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">></FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">> b. XML based data model</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">> - Tamino (optimized for XML storage/retrieval)</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">> - Xindice (optimized for XML storage/retrieval)</FONT></SPAN> </P>
<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">Xindice is optimized for storing a large number of smaller XML documents.</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">AFAIK these document itself are not organized hierarchily. Please correct if</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">I am wrong.</FONT></SPAN> </P>
<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">> - Excelon/Object Design</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">></FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">> c. Relational data model (optimized for Relational storage /retrieval)</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">> - Oracle</FONT>< /SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">> - Sybase</FONT>< /SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">> - SQL Server</FONT> </SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">> - MySQL (opensource !)</FONT></SPAN> </P>
<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">That will probably be the way to go (at least at the beginning.)</FONT></SPAN> </P>
<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">> - DB2</FONT></SPAN> </P>
<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">Thanks for comment,</FONT>< /SPAN> </P>
<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">Florian</FONT></SPAN> </P>
<P><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">=============================== ============================================</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">To unsubscribe, send email to listserv@(protected) and include in the body</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">of the message "signoff J2EE-INTEREST". For general help, send email to</FONT></SPAN>
<BR><SPAN LANG="en-us"><FONT SIZE=2 FACE="Arial">listserv@(protected) and include in the body of the message "help".</FONT></SPAN> </P> </UL> </BODY> </HTML> =========================================================================== To unsubscribe, send email to listserv@(protected) and include in the body of the message "signoff J2EE-INTEREST". For general help, send email to listserv@(protected) and include in the body of the message "help". <p>
|
|
 |