Ryan's Journal

I've been exploring open source Java persistence frameworks for the past couple of days. People seem to love Jaxor, but I ran into problems immediately: there's no way to block or redefine default get/set JavaBean methods, and there's no way to map multiple tables (in one-to-one relationships) to one Jaxor entity. These are things that can be worked around, but they require mucking with generated code or creating and strictly adhering to protocols of non-idempotent JavaBean use. Those are bad things. The documentation is a little weak, which is another poor selling point; I couldn't answer the above questions without actually trying to work around them.

I immediately fell in love with Jaxor's code generation (I could run parts of an already existing test suite ten minutes into my venture), but it fails on points it should really be covering.

For a quick and simple project, I think Jaxor would serve pretty well. The question is, is there such a thing as a quick and simple project?

You must login to leave a comment