Vedovato Paolo wrote:
Hm... not sure if that's realistic. Switching with minimal code changes, yes, but with no code changes I don't know. For example, *Aware interfaces should be gone. We might want to reconsider how context and pre/post processing is done too. For example, it would be entirely possible to use Action implementation wrappers instead of ActionFactory delegates (i.e. do stuff on execute() instead of on getAction()). Since I think most of us are seeing needs for that already (e.g. validation, security, various pre-processing) that would be a nice way to handle it. And it could also be an alternative way to do chaining.I think that it's a very important point to be able to switch to XWork without having code changes AND to have all the improvements (like performance etc.).
Really Fast Usage of XWork is not the primary concern IMHO. I would MUCH rather have XWork be AS GOOD as it can be from both design and performance point of views, and have usage delayed somewhat. Having a compromised solution that only goes half the way is only going to hurt in the end.So if there is extra work to achieve this it should really be considered. That would lead to a really fast usage of XWork through the WebWork community.
/Rickard
--
Rickard Öberg
[EMAIL PROTECTED]
Senselogic
Got blog? I do. http://dreambean.com
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
