Regarding: "We do plan on having the same sort of thing, enabling Xwork Actions to be the Actions backing JSF. I have it assigned to me, but I haven't really seen enough JSF interest to make it a priority pre 2.0 release..."
I have been following JSF for a while, and have looked at the Struts support for JSF. Maybe I will work on this piece of WebWork in my spare time. It sounds like a lot of fun. I think interest in JSF will explode at some point this year. "Yep, we like IoC too... Xwork IoC is nice for simple apps because you don't have to create new meta-data for every Action, it just figures out the dependencies based on the Interfaces implemented. That said, it starts to hold you back as your applications become more complicated, which is why our integrations with both Picocontainer and Spring are important." WOW! Interesting tack. Hmmmmmmmmmm.... Why not just add the best of breed features in XWork? Is it because Spring is so far along and feature rich regarding IOC, AOP, and the rest? P.S. I did not realize when I selected digest mode that I would only be getting digest mode. I suppose I could sign up for both. ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
