My experience echos Ted's...
I just recently completed a relatively small webapp where data the user
entered had to run through a series of rules, and the rules were
tailored to a specific client. And, it was a all-or-nothing situation,
i.e., the data either passes all the rules or fails if any one rule
fails. A CoR pattern seemed like the obvious solution, and that's how I
wound up doing it, to great success (although I used the CoR
implementation in Java Web Parts because it has some added capabilites,
but it's the same underlying concept).
As Ted says, I execute the Chain from an Action, treating it just like
any business facade. While I could see having a Chain be an Action in
some cases, executing the Chain from an Action (or business delegate
maybe more likely) I would suspect will be the most common usage pattern.
Not that any of this answers your original question Wendy :)
Frank
Ted Husted wrote:
On 12/8/05, Wendy Smoak <[EMAIL PROTECTED]> wrote:
Then in Extras we have ChainAction and DispatchChainAction. I assume
I'm supposed to use one of those instead of including a special Action
in my webapp.
I don't think anyone knows what we are "suppose" to do yet.
Personally, I'd lean toward calling Chain from an Action, like any
other business facade. I don't see the value-add in mixing the
business chain in the with presentation layer. I've been using a port
of Chain very successfully in ASP.NET just by calling it from the
equivalent of an Action. I also used this approach in the (unfinished)
Chain MailReader in the sandbox.
I haven't tried the new Struts Chain gizmos yet, so I can't help you
on that score. :(
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Frank W. Zammetti
Founder and Chief Software Architect
Omnytex Technologies
http://www.omnytex.com
AIM: fzammetti
Yahoo: fzammetti
MSN: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
