Even if you do have an existing schema, it's not too hard to use GORM DSL to map the schema to a grails application. You can see an example of that in a blog entry I wrote: <
http://blog.javabilities.com/2009/06/access-legacy-database-using-gorm-dsl.html>. I can't speak to using JPA though, this is just using GORM DSL to map to a legacy database.
Lloyd
On Tue, Jun 30, 2009 at 3:50 PM, Ed Young
<ejy@...> wrote:
I'm on a project where we are considering which web framework to use for a system that has a nascent EJB3 persistance landscape in development. Tomorrow (July 1) we will have a discussion about which is the best framework for our project.
Seam is the competing framework and no surprise, there are strongly held opinions, some more valid than others. Interestingly there is no one at our shop with any real Seam experience, but it is non the less favored by some anyway.
The main issue seems to be that there is a EJB3 persistance model being developed and the argument is that Grails will have to circumvent the EJB3 technology while Seam is designed around EJB3, and JPA.
I have alot of Grails experience, but all of it greenfield db development. No legacy mapping, and no EJB3. I wonder how much of an issue this is in reality. Trust me, I'm scrambling to learn all I can asap.
I see that there is some coverage in DGG chapter 17 "Legacy Integration with Hibernate":EJB 3 Compliant Mapping and I plan on looking into this to diffuse that argument, hopefully. Can anyone point me to any other resources for this kind of issue?
So, is the EJB3 deal breaker in favor of Seam?
Also, it may be argued that Grails does not have mature JPA support? Can anyone speak to this issue?
Also, what other points can there made to argue for Grails over Seam in this instance?
