Interesting, but how would you provide transactional isolation so you do not experience phantom or dirty reads?
2009/10/6 Igor Vaynberg <igor.vaynb...@gmail.com> > i think all the suggestions you have gotten until now are > overcomplicated and have a high learning curve. i think the easiest > and fastest way to achieve persistency is to use a database that all > operating systems already have - the file system. > > each "table" is a directory, each "entity" is simply a file that has > the serialized state of that entity named something like <uuid>.ser. > > done. its easy and simple. most importantly, there is absolutely no > configuration needed other then "the root folder" and nothing to learn > other then being able to read and write a file. > > if you want to take it up a notch you can use something like xstream > or jaxb to serialize your entities into xml - which will make > debugging easier. > > -igor > > > On Tue, Oct 6, 2009 at 2:34 AM, Peter Arnulf Lustig <uuuuu...@yahoo.de> > wrote: > > What's the fast and easy way? > > > > I am asking because of a lot of trouble with hibernate. > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > > For additional commands, e-mail: users-h...@wicket.apache.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
