Actually, for anyone serious about hibernate, I'd recommend Java Persistence With Hibernate:
http://www.amazon.com/Java-Persistence-Hibernate-Christian-Bauer/dp/1932394885 You learn a *lot* about ORMs in general as well as the details of JPA and Hibernate. It was the precursor to this that I read a few years ago when I started working on my own baby ORM and it really helped to explain all of the concepts. Best Wishes, Peter On Mar 3, 2009, at 2:21 AM, Alan Livie wrote: > I've been playing with Groovy and Hibernate for about a week now and > what is brilliant about it is when building something from scratch > you no longer think about the db in the way you do usually. > > You just create a database and forget about it. You focus on your > domain model, adding a few Hibernate annotations along the way and > when you call save() in your Hibernate session it creates tables, > columns and saves all the data. Inheritance hierarchies etc not a > problem. > > If cf9 can work with Hibernate in the same way (maybe annotations in > cfscript and/or a new attribute on the cffunction tag) then in a > year or two no one will even care about DAOs and Gateways. > > If you want to understand things like Data mapper, Unit Of Work etc > to get an idea of what Hibernate is doing then read Fowler's > Patterns Of Enterprise Application Architecture ... then be thankful > someone else has done the ORM work because it looks like a complete > nightmare trying to build an ORM! > > Alan > > > From: Jaime Metcher <[email protected]> > To: [email protected] > Sent: Tuesday, March 3, 2009 12:07:02 AM > Subject: [CFCDEV] Re: Presenting on OO - Should I show the "Gateway" > pattern? > > > John, > > Can I just throw in the cautionary note that the persistence layer > is often > where *all* the design compromises end up, and especially in > ColdFusion is > where the non-OO world really refuses to be ignored. Because we all > spend > so much of our time with data-centric apps you've got to cover it, > but I > would always be saying up front that this stuff is not really where > the OO > rubber hits the road, it's actually about the worst place to start > when > learning OO, and a student should definitely not be extrapolating > what we do > in the persistence layer into a set of general OO design principles. > > Jaime > > > -----Original Message----- > > From: [email protected] > > [mailto:[email protected]] On Behalf Of John Whish > > Sent: Monday, 2 March 2009 7:54 PM > > To: CFCDev > > Subject: [CFCDEV] Presenting on OO - Should I show the > > "Gateway" pattern? > > > > > > Hi all, > > > > I've started doing a 00 101 course for my CFUG, part one went > > well and the feedback was that they want to know about the > > persistence layer next. > > > > I want to cover the main patterns and emphasise that there > > are multiple ways to do it (not just DAO, Bean and Gateway). > > I'd like to do do ActiveRecord, DAO, FlyWeight and Iterator > > patterns (although it might have to be split over 2 > > presentations) and introduce the "gateway" as a ColdFusion > > specific pattern that is used for speed rather than being OO. > > > > I did the classic example of showing someone's age in my > > first presentation and said how you should avoid putting > > functionality into the view, however if I show the "gateway" > > approach, I'll be back to putting it in the view. That just > > doesn't feel right to me when I'm trying to preach good practice. > > > > Thoughts appreciated :) > > > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CFCDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/cfcdev?hl=en -~----------~----~----~----~------~----~------~--~---
