[Lift] Re: Big Domain Model - Lift and Persistence

2009-04-10 Thread Tim P
more a scala question this: but with the JPA can I create Traits that encapsulate the annotations for example an Id trait that includes @Id. Any obvious drawbacks in doing so? Thanks Tim --~--~-~--~~~---~--~~ You received this message because you are subscribed to

[Lift] Re: Big Domain Model - Lift and Persistence

2009-04-10 Thread Derek Chen-Becker
I've only ever done something like this with the joined subclass support in JPA, so I don't know if using raw traits for independent classes would work. Easy to test, though. Derek On Fri, Apr 10, 2009 at 5:38 AM, Tim P tim.pig...@optrak.co.uk wrote: more a scala question this: but with the

[Lift] Re: Big Domain Model - Lift and Persistence

2009-04-10 Thread Charles F. Munat
I've been wondering about this, too, but too busy to experiment. Please post your results if you try it. Chas. Derek Chen-Becker wrote: I've only ever done something like this with the joined subclass support in JPA, so I don't know if using raw traits for independent classes would work.

[Lift] Re: Big Domain Model - Lift and Persistence

2009-04-09 Thread Derek Chen-Becker
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