Thursday, February 20, 2003

Hibernate Rocks I see this again and again, and appears to be why Hibernate has such high mindshare! Two hours ago I decided to learn how to use Hibernate. I just got a test app to run using Hibernate and I found it to be a shallow learning curve. Hibernate is already at the point where I eventually wanted DataBind to be. I guess this spells the end of DataBind which doesn't bother me one bit. :-) [All Things Java] 2:20:49 PM

Castor links. I've been holding back on using Roller for two reasons: one is the lack of Metaweblog API, and the other is the choice of O/R technology. Nobody talks about Castor, and all the mindshare appears to be around Hybernate. I personally like Torque, and perhaps with the recent reorg of the db.apache.org site, it may get more exposure. Roller uses the Castor persistence framework. FreeRoller can be very slow. Are the two things related? I have no real empirical evidence (yet) to prove a link, but I did find an interesting link of a different sort in my referer logs this morning to a blog entry by (Roller user) Matthew Porter. Back in December 2002, Matthew chose Hibernate instead of Castor for the Java Lobby Community Port (JLCP) project. Here's why: Persistent Framework Choice for JLCP: Castor was not chosen for two primary reasons. The first is the lack of development of Castor in the past year. In addition, one the tests we performed at DMI, Castor was significantly slowerthan other PFs- to the point where it was intolerable. The first reason and recent tests led me to believe that the situation regarding speed had not changed. Also, an interesting link was posted in a comment on my Long Transactions post yesterday. This is a pretty interesting article: O/R Mapping with Castor JDO in the Real World: Castor holds up to its promises in simple testing and trial runs. However, it has proven to fall short in some practical issues with our application of about twenty-five data classes and as many tables. Most of our problems come from the need to hold onto objects across transactions and perform complex updates. I'm tempted to rewrite the Roller backend using Hibernate just for the hell of it, but I really should to do some profiling of Roller to see where the problem lies, don't you think? I guess I could do a 30-day eval of OptimizeIT or JProbe, but I would be happy to hear your recommendations for free and/or open source profiling tools. Got any? [Blogging Roller] I wish I had the bandwidth to offer my support! 9:51:06 AM