IMHO I'd stay away from compiler's plugins (in this context) not because I don't like them ... but it's just another thing that potentially makes a bitter Lift users experience. Not to mention potential problems that raise with IDE's integration (extra configs etc.).
.. but I hope I'm wrong. Br's, Marius On Nov 28, 7:41 pm, Tim Perrett <[EMAIL PROTECTED]> wrote: > > So if a general JPA integration proves to be hard then I see value in just > > having seamless integration of JPA/hibernate with Lift features. And if > > somebody wants to use other JPA-impl, they can always use it just the way > > they can use it today. > > This is a fairly good point - seamless integration is important, if > thats what we support, more often than not people will go with what we > support. > > Derek: as you are the JPA with Lift guru, what is your gut feel? If a > compiler plugin yeilds a slicker implementation, but is a little more > work, then we should go with that. However, if using the hibernate > stuff yields a slick enough solution and doesn't give users ugly > looking code, then sure, i think it could be an acceptable solution. > > Cheers, Tim --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" 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/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
