Hey guys,

I've now posted a news item on the website, and fixed up the download links to the 1.0 release.

The past two days I've given a couple of seminars on Qi4j in association with the JFokus conference in Stockholm. The seminars focused entirely on the issues with using POJOs for domain modeling, and how using composites and mixins brings a much better approach to it all. The audience was very familiar with what I described, and agreed with all the issues and examples I presented, so there wasn't much resistance to the conclusions.

The main resistance is the continued reliance on relational databases for storage, which seems to be an issue we really need to address in order to get more widespread usage. Yes, it is suboptimal, yes it will be more work to use, but there it is. Also, several people told me not to try and base our RDBMS support on Hibernate, as they claimed it was basically broken in terms of semantics. Some horror stories were provided, and I can sympathize with them.

So we're still back at what to do for RDBMS? Hand-coding or something like iBatis seems like the best option. What others are there?

In any case, GREAT job everyone! It's nice to have this out the door, so we can start focusing on how to get more people to try it out, and get more experience with how to best use it.

/Rickard

_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev

Reply via email to