this is due to the XSD file currently not available online. We’re going to publish them under the URL declared in the XSD as soon as possible.

A workaround would be to either check out the sources from SVN or extract the XSD from the binary distribution and a custom entry to your Eclipse XML catalogue.

Please let me know, if you have trouble getting this working.

Regards,
Ollie

P.S.: A dedicated forum for our open source projects is on its way ;)

I filled my email address at the email field of the ‘write a comment’ box (but I also spent some considerable amount of time to find out yours with no success ;) My mail is [removed to ensure privacy] but we can have a quick chat on either google talk, msn or skype (message) as well.

I’ve seen the Spring Assert class in PageImpl..

cheers,
Kristof

thanks for sharing your thoughts on Hades.

Could you elaborate on where you found the Spring Assert in the domain package? I just took a quick glance and couldn’t find one. Normally I tend to only use Spring Asserts only in classes that have are intrinsically tied to Spring anyway.

Using String.format() is a good idea. I just filed this as a ticket: http://trac.synyx.org/hades/ticket/30

Your concern towards the setter is legitimate. I very often use it during mapping DTOs to domain objects and in test cases. But as the main purpose of AbstractPersistable is to free the developer from standard JPA Id declaration, we could leave the decision how to expose the id to the domain class developer. I’ll try to remove the setter in the trunk to see how it feels.

Regards,
Ollie

PS: I’d like to take a glance at your criteria API stuff. If I knew how to contact you, I definately would.

I checked out Hades and I like your coding style (and clean docs) though I’d like to add a few comments:
- using Spring’s Assert class binds even the entity base classes to Spring way too closely
- you could use String.format() in toString() methods as well
- AbstractPersistable’s getId/setId (especially the latter) being public by default exposes a bit too much (breaks OO encapsulation in certain cases)

Would you be interested in having Guice support as an option beside Spring? Also, recently I’ve been working on implementing the Active Record pattern and a typesafe criteria API on top of JPA, if you’re interested, drop me a line.

Don’t hesitate to make suggestions for improvements or get your hands on directly.