tag:blogger.com,1999:blog-374912558765682533.post4929600303693526448..comments2023-10-26T04:32:46.845-07:00Comments on Marcel Overdijk's Blog: Spring Roo vs Grails generated controllersMarcel Overdijkhttp://www.blogger.com/profile/12010344238448200902noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-374912558765682533.post-1329690334677292992010-01-05T05:17:33.528-08:002010-01-05T05:17:33.528-08:00@Franki: I think mainly for people who can't u...@Franki: I think mainly for people who can't use Groovy/Grails because of company restrictions.Marcel Overdijkhttps://www.blogger.com/profile/12010344238448200902noreply@blogger.comtag:blogger.com,1999:blog-374912558765682533.post-64579738037761973712010-01-05T05:15:54.438-08:002010-01-05T05:15:54.438-08:00I'm a Grails developer. I would prefer SpringS...I'm a Grails developer. I would prefer SpringSource unify efforts in a more powerful framework rather than disperse in two frameworks. What is the motivation for Roo?Frankihttps://www.blogger.com/profile/11200477790599745507noreply@blogger.comtag:blogger.com,1999:blog-374912558765682533.post-75329382535660413432009-11-16T12:14:09.126-08:002009-11-16T12:14:09.126-08:00@Vernon: Spring Roo 1.0.0.RC3 contains reference d...@Vernon: Spring Roo 1.0.0.RC3 contains reference documentation. Check out part III. Internals and Add-On DevelopmentMarcel Overdijkhttps://www.blogger.com/profile/12010344238448200902noreply@blogger.comtag:blogger.com,1999:blog-374912558765682533.post-84846967683610327102009-11-16T12:14:09.127-08:002009-11-16T12:14:09.127-08:00Is there any documentation you would recommend for...Is there any documentation you would recommend for writing a new plugin for roo?Vernon Singletonhttps://www.blogger.com/profile/09612077916175875470noreply@blogger.comtag:blogger.com,1999:blog-374912558765682533.post-58979730526384369772009-11-16T12:10:03.367-08:002009-11-16T12:10:03.367-08:00Is their any documentation you would recommend for...Is their any documentation you would recommend for writing a plugin for roo?Vernon Singletonhttps://www.blogger.com/profile/09612077916175875470noreply@blogger.comtag:blogger.com,1999:blog-374912558765682533.post-43816957976318179962009-10-25T15:07:47.464-07:002009-10-25T15:07:47.464-07:00Roo now generates ITDs that use proper imported ty...Roo now generates ITDs that use proper imported types, so they look quite natural. So one of your concerns about Roo has been fixed as of Roo 1.0.0.RC2 and above: http://jira.springframework.org/browse/ROO-177<br /><br />The other item to note is the code Roo generates is 100% standard Spring/JPA/JSP/Maven etc. This means there is zero learning curve for anyone already experienced with the normal Java stack. Finally, with Roo you can "push in refactor" and get rid of Roo from the project in < 3 minutes. You're left with stock-standard Java code just as if you'd written it yourself.<br /><br />Roo also does not exist in the runtime. So a Roo app is going to be very fast and memory efficient. Plus its use of AspectJ compile-time weaving means there aren't even AOP proxies needed, resulting in further performance and memory optimizations.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-374912558765682533.post-84688218407970215092009-10-07T05:18:31.178-07:002009-10-07T05:18:31.178-07:00SpringSource should really invest more resources i...SpringSource should really invest more resources in enhancing Grails than building another framework...<br />I think the argument: "If you are not allowed using Grails in your Company, use ROO" is not valid. As Roo has its own learning curve like any other framework. Managers make descisions based on cost effectiveness, learning curve, protection of investments and few others. And ROO is definitely competing with Grails. And having two Agile Frameworks in the product portfolio is confusing developers. SpringSource: DECIDE!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-374912558765682533.post-43956508037990890842009-07-22T16:30:14.011-07:002009-07-22T16:30:14.011-07:00It would be great if SpringSource invested more in...It would be great if SpringSource invested more in Grails (eg: IDE's, hiring more core developers, etc) rather than creating a similar (probably better in some scenarios, but similar) framework.Alvaro Sanchez-Mariscalhttps://www.blogger.com/profile/05857828289901496399noreply@blogger.com