I would use the package names as directories and the class names as the inner most directory name (with a capital). This immediately makes it an ORM solution. Inheritance hierarchies can be created by symlinking the instances to each super type's directory.
Martijn On Tue, Oct 6, 2009 at 11:02 PM, Igor Vaynberg <[email protected]> wrote: > 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 <[email protected]> wrote: >> What's the fast and easy way? >> >> I am asking because of a lot of trouble with hibernate. >> >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.4 increases type safety for web applications Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.0 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
