The Hibernate Validations section is in there to show one approach. Given the breadth of people's requirements for validation it would be hard to say that one way is always preferable over the other.
On you original question, my experience with Mapper says that for a schema that big (and, I'm assuming, correspondingly complex in terms of joins and relations) then JPA will be easier to work with. The tradeoff is that you'll have to do the validation and form handling yourself. Derek On Thu, Apr 9, 2009 at 12:56 PM, Tim P <tim.pig...@optrak.co.uk> wrote: > > Hi > I'm embarking on a web project with a big domain model (50+ classes - > supply chain application). > I was all set to go using a combination of Java domain classes, a bit > of mixin via ClassFileTransformer, Hibernate and Grails as a web > framework. > Someone said "if you're looking at mixin look at Scala, and it's got a > web framework too" > so I arrived here about 2 hours ago (still printing out the book). > > Is anyone using Lift for a project like this? Any comments on > applicability? And would you use the native mapper mechanism or jpa as > in the book if you did? > > Grails is clearly miles ahead in terms of documentation and community > size, but the lack of type safety in groovy really irritates me (hence > the class files in Java). > > any comments? > > also my quick scan of the book shows a mix of hibernate validators and > scala. Any reason why using annotations is good for this, if it could > be done in parent classes instead? > > Tim > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
