Just noteThe base of the code is from the Groovy Servlet implementation and I've kept the good parts (compilation of all scripts and dependencies is done automagically). If you just want to do servlets php-style but keep the xwork interceptor mechanisms, just put all code in the view, but that breaks the design patterns. :)
In your's blog you haven't mentioned anything about groovlets (aka groovy +
servlet). They are somthing like servlets but much easier to use and is very
like php. It needs only to add a groovy servlet and map all request with
*.groovy. Evrything else will be handled automatically.
Now webwork2 for UI tags is using velocity. It means that for every ww:uiInitial benchmarks show that the Groovy script implementation is about 50% slower than the Velocity equivalent. It seems to be that the on-the-fly generated classes are slow. I see a lot of reflection going on in groovy.land.MetaClass. I'll ask the Groovy guys about it and it will probably be sorted out. If there's a difference between these classes and the pre-compiled ones, we should at least be able to switch to precompiled on deploy time. :)
tag there is velocity involved. With groovlet it is possible to easily
replace all velocity templates in just one day or two the most (at least I
hope :) ). And because grooblets are bytecode and they are cached by groovy
servlet there I expect some performance imrovment. And it is still possible
to use full pover of java language.
Dag
------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
