Yes, but I think it brings a lot more to the table. For example,
Action inheritance chains would be a thing of the past. Any common
code could be changed into a command and placed in the chain.
Yes this will definitely be nice. I don't currently do a lot of this
now but I could see how it could come in handy if you have a lot of
Actions inheriting from one another (or calling one another.)
You could even easily create a command that, instead of executing an
Action's execute method, calls a custom method on a POJO like JSF
(I've done some experimenting here:
http://www.jroller.com/page/mrdon/20040706#zero_configuration_with_struts).
The POJO's setter methods could even be called using request data,
removing the need for action forms.
I thought about this but I wonder how easy it will be to drop the use of
ActionForms. They currently provide some nice functionality that would
be missed.
Of course much of this is possible with the current Struts by
extending RequestProcessor, but that approach had a number of
disadvantages:
1. Extra work (two extensions) to support regular and tiles RequestProcessors
2. Couldn't co-exist with any other extensions
3. Hard to test
Yes this will be sweet! So you can easily pick and choose your
extensions and add new ones. Will there be subtle issues (like the
order of the command chain) for tiles and validator to work properly?
Furthermore, and perhaps most importantly, Struts-chain brings with it
the potential to remove the Servlet dependency, making it easy to run
your Struts app in a portlet or any other container.
If you remove ActionForms, Actions and the Servlet dependency, is it
really Struts anymore? Most of my logic is currently already outside of
the Actions (I use the facade pattern.) Wouldn't it make more sense
for me to chain my business logic behind the facade? Ultimately I'm
still writing a web application, so how do I get away from the "Servlet
dependency?" I think I see where you are going with that statement but
I'm not sure about some of the details. Can you help me to understand
how you see this working?
Thanks,
sean
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
