Link Details

Reading the comments I wonder if the tools and the Grails concept are enterprise-ready.

Grails is being used in enterprises very successfully now. I've used it in three different enterprise "java shops" and I know of others who have as well. Integrating different frameworks that often have overlapping functionality will always be more difficult than working with any one framework by itself.

Many of the comments had to do with Maven integration, which is newer and still has some rough spots (though the case could be made that Maven has its share of rough spots too :)

Grails is basically a much more productive way of using Java frameworks that are already predominant in the enterprise, so I think the short answer to your question is "Yes. Grails is enterprise-ready".

So the point of the article is that "Grails make sense", because one can write spring beans, JSF components and XML with groovy? Or what?

Many people at many organizations have seen and acknowledge the productivity gains that can come with using Grails but have been hesitant to adopt it because it's not a "Java framework". My point is that excuse doesn't make sense and that taking advantage of Grails does make sense.

I see. This means that an argument along the lines of "we can't use grails because it's not a java framework" does not make sense, agreed - note though that this doesn't imply that it *makes* sense to use grails (unless that indeed was the sole reason for not using grails).

I see your point. I do think that Grails makes sense for a host of reasons, but that wasn't the point of this particular post. I guess I took a bit of creative license with this title. :-)