I don't know if we'd really need to support GSPResult in a Struts 2 Plugin. AFAIK, the slowest part of Grails is GSP.
http://tinyurl.com/2298jh If we were to write a plugin, would it implement the same scaffolding that Grails has by default? If so, it might be better to use FreeMarker since that seems to be a recommended choice among Struts 2 developers. I don't believe there's a FreeMarker Plugin for Grails, but I'd be interested in creating one. A colleague of mine has been successful in making Grails work with JSP. Matt On 11/12/07, Philip Luppens <[EMAIL PROTECTED]> wrote: > On Nov 12, 2007 3:57 AM, Tom Schneider <[EMAIL PROTECTED]> wrote: > > See my comments below: > > > > Mark Menard wrote: > > > On 11/11/07 5:07 PM, "Tom Schneider" <[EMAIL PROTECTED]> wrote > > > I will agree with you, and I've decided I'm done reinventing wheels. So, > > > I'm > > > game. I'm very pressed for time, but I'm definitely interested in this. I > > > think a bridge from Java based Struts 2 development into Groovy is really > > > exciting. We have realized some serious productivity gains using Groovy > > > with > > > Struts 2 in the simple way we've been using it in house for some time now. > > > > > Good, I'm glad we're on the same page. I really liked some of the stuff > > I saw with Groovy/Grails. No rush here, I just wanted to throw this out > > there in case anyone else was interested in pursuing this. (Don > > expressed interest at one point) > > >> 3. A GSPResult that can create the context for the GSP page and execute > > >> the GSP page. > > >> > > >> I did some work on this over the weekend and it didn't take too much > > >> effort to get a GSPResult going. (Although the templated executed, it > > >> didn't display any data because I didn't have a ModelAndView for the > > >> template to run against) > > >> > > > > > > I think someone has done a GSP result. It might make some sense to look at > > > that. > > > > > Close, but not exactly a GSPResult: > > http://struts.apache.org/2.x/docs/groovyresult.html > > Ok, I'll jump in for a moment. The difference between GW (GroovyWorks) > & SS (Scripting Support) is indeed the Spring requirement. I took the > GroovyScriptEngine object and build the plugin around it - extremely > easy, but no Spring integration, and it only allows for writing > actions and interceptors in Groovy. Which, imho, was more than enough > at that time. I also met Mark at that time, and saw that once Spring > got its act together, it would quickly surpass the SS project. I can't > imagine any project not using Spring integration, but at that time > > I messed around with the GSP Result as well, but at that time, GSP > just being moved from being a seperate project, to the Grails > codebase, and it was not easy to track down its status. So I gave up > there. At that time, there weren't any real benefits to it either > other than just being a new view. > The groovy result has nothing to do with GSP, it was done way before > that. I simply needed dispatching to a script (don't ask, had some > weird requirements back in the days), and so I used that one. Think of > it as a first step towards the SS project. > > Cheers, > > Phil > > -- > Software Architect - Hydrodesk > "Always code as if the guy who ends up maintaining your code will be a > violent psychopath who knows where you live." - John F. Woods > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- http://raibledesigns.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
