a realy stupid question, is it possible to map a tamino database with an schema to a hibernate object?

Tamino is one of those XML "databases"? I don't think that this is possible, after all it is not a real database, just a marketing joke. Basically, you can use a database with Hibernate if it has a JDBC driver.

Hi,

If you need to store XML data, maybe you could see XMLPersistence. It uses Hibernate to map to a Relationnal database.
I never used it, only discover it a day...

http://www.xml-persistence.net/en/

If you try it, I would appreciate to have some news about it...
Thank you

Charles

There is no difference between XML "data" and a simple text file. Don't use XML for data management, you may as well use comma separated values in files.

Or maybe you could try eXist (open source) http://exist.sourceforge.net

or Xindice http://xml.apache.org/xindice

I disagree with you christian. Because an XML database use indexing and can work in a transactionnal environnement, you can't do the same with a text file!

Sorry, but this is just not true. I can lock and release a textfile just the same.

For sound data management you need a data model. This model gives you

a) a well-defined structure that removes data redundancy
b) a "sufficent" set of constraints to ensure the integrity of your data
c) a set of well-defined operations to manipulate/query your data

XML as some a), very little b) and the little it has of c) is unneccessarily complex. If you compare that with the relational model, you will be surprised how bad XML (and object database, for that matter) is for data management and how marketing makes many people think differently.

Having transactions (which is quite trivial to implement if you don't need performance) has nothing to do with the data model, it's an implementation detail of the data management system.

The first thing I want to say is that I totally disagree in using a native XML database or object database as a main database. But, in some cases (and they are not so little) using an XML database could be a better way than using a relationnal database.

For example, if you want to store a hudge number of XML document and do some work with it (inserting, some updates, searching or deleting), it would be better using an XML database than a relationnal one that would be always mapping all the resources and maybe be just a little slower than a database thought to manage XML data... don't you agree?

yeah you're right,

in our system we use a xml database to store metainformations of experiments. And the experiments coud be realy variabel and so a xml database was the best choice. ok at first I also why we need this... But now its fine and we working on a technique to query the xml database from our relational database.