Not necessarily. Some people propose relacing Actions with Commands,
but I see Commands as more to do with request processing in general,
than request-specific business logic. Instead of a ExecuteAction
command that executes a regular Struts Action, you'd have
ExecutePOJOAction which calls your o
On Wed, 15 Sep 2004 17:49:21 -0400, Sean Schofield
<[EMAIL PROTECTED]> wrote:
> >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/200
The best part for developers is commands are very easy to write, and can be easily unit tested.
I'm assuming then that your thinking about replacing most of your
Actions with Commands and the commands would work with POJO's in your
Context right? Would you use a facade as well or would you t
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 c
Yes, you have complete control over everything that happens in a
request. The chain can even be modified at runtime to adjust as
necessary. Struts-provided commands could replaced and/or new
commands could be added to perform some specific purpose. I even
envision new "sub-frameworks" that write
Exactly. It really changes the way you design your application, and I
think in a great way. It would be great to get more people using it
to help flush out any remaining problems with it.
That's kind of what I gathered. This could potentially be a really big
change in the way Struts applica
At 4:13 PM -0400 9/15/04, Sean Schofield wrote:
I've been taking a look at the new struts-chain in the contrib
section. It looks intriguing but I can't quite figure out what its
for and how I might use it. It seems like it will ultimately
provide a replacement for RequestProcessor by decomposi
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. You
could even easily create a command that, instead of executing an
Action's execute method, calls a
8 matches
Mail list logo
