> NABETH Thierry wrote:
> I must say I am a little bit worry that Jetspeed evolves too much
> towards
> the old software architecture in which you have a kind of central
> relational
> database around which the application are developed. (and as
> consequence
> complexity, and lack of flexibility).
Don't worry... same here. :)
> (Note that I very much like the architecture of Jetspeed right now,
> because
> it separate very well the logic of the application and the
> presentation).
>
> Have someone thought of going more towards the idea of using a model
> of persistance ?
> (this way the database is directly an extension of the object oriented
> "paradigm").
Yes. This is a much larger problem than storing data in the DB. We
need to have XML stored in a round trip fashion but we also need to be
able to run under all databases (Oracle, etc).
It is a large problem.
> For instance have a look at this article:
>
> "Objects in the Database: An overview of Sun's Java Data Objects
> specification"
> by David Jordan
> Java Report, June 2000
> The main objective of JDO (JAVA DATA Objects) is to provide support
> for
> transparent object-level persistence of Java objects, so that Java
> class
> developers need not provide their own persistence support.
> The JDO API is defined such that applications are independent of the
> particular
> data store being used by a JDO implementation. Implementations are
> planned for
> file systems, hierarchical, relational, and object databases. These
> will be
> available in the following Java environments.
> http://www.javareport.com/html/from_pages/column.cfm
>
> Castor (Exolab) seems also to go to this direction with
> Castor JDO: Java object persistence to RDBMS
> http://castor.exolab.org/JDO
It really isn't just Java Data only. I want to store XML right in the
DB but retain all the advantages I had from a conventional relational
model. Castor JDO approaches this. There are also some competitors to
JDO.
> I would also like to mention another open source initiative called
> Zope
> http://www.zope.org/
> in which an object database is directly integrated into the system.
> Zope is writen on top of python, and does not really rely on xml,
> which is why I believe the future of Zope is relatively limited.
yup.
> However, zope has a lot of flexibility I would have liked to find
> in Jetspeed.
> You can directly browse your (OO) database with a web browser
> as you would do with a filesystem. (except that the categories of
> objects
That is beyond the scope of Jetspeed.
> >
> > Does anyone know if it's still possible to run w/o a database?
>
> Jetspeed can no longer be run without a database. We made it a
> requirement because we needed the functionality a DB provided.
>
> Hypersonic SQL (an in-memory db) will probably ship as the default
> database so that you don't have the long configuration times.
It is important to understand that we really need a conventional DB for
Turbine. This is another project on with Jetspeed is based. Our
persistence mechansim is probably going to be based on a blend of XML
and relational. Watch this space...
Kevin
--
Kevin A Burton (e-mail: [EMAIL PROTECTED], UIN: 73488596, ZKey:
burtonator)
http://relativity.yi.org
Message to SUN: "Please Open Source Java!"
To fight and conquer in all your battles is not supreme excellence;
supreme
excellence consists in breaking the enemy's resistance without fighting.
- Sun Tzu, 300 B.C.
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
