Mailing-List: contact dev-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Developers List" <dev@struts.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of dakota.jack@gmail.com designates
 64.233.162.199 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=m2BoBpxwJTSeIDOW15bFpEn3rXMp0360nJC8NTjMlHWe5rXmkc+rLMGHR2qwQSuXj1aoHVHul4MLc9YJkfgKu0x50tAw4V63BUlf4nL72ljFuBfQZolLCAReTvRVOYHIgP6jfU/W7y1Dzj38UBaiL+zPJbfICR038M4jtBhzJSs=
Message-ID: <e03014300602182158x3033db19r8716ebfe03fe9c92@mail.gmail.com>
Date: Sat, 18 Feb 2006 21:58:08 -0800
From: "Dakota Jack" <dakota.jack@gmail.com>
To: "Struts Developers List" <dev@struts.apache.org>
Subject: Re: Reasons for 1.3 release
In-Reply-To: <43F55CCE.10507@omnytex.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_1011_2745832.1140328688880"
References: <1db115340602160939p2a5106a1m8066656906cac711@mail.gmail.com>
	 <61931.170.201.180.136.1140111783.squirrel@webmail.chiron.lunarpages.com>
	 <1c661f2f0602160949n6274dbdfy406a43a77b8f57a3@mail.gmail.com>
	 <1db115340602161218v57e048b8ma90bb90befc37239@mail.gmail.com>
	 <16d6c6200602161252s59025139i6ae0a4fa30208994@mail.gmail.com>
	 <1db115340602161304m4f6d09ccs2736ae1254263f5@mail.gmail.com>
	 <16d6c6200602161320t9cbc708j442cb4a89abf27c9@mail.gmail.com>
	 <23679.170.201.180.136.1140125248.squirrel@webmail.chiron.lunarpages.com>
	 <f8b39ace0602161439u1a219100p60aa6e50a6eed312@mail.gmail.com>
	 <43F55CCE.10507@omnytex.com>

------=_Part_1011_2745832.1140328688880
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

The flexibility is clear.  But, from what I can see the pattern is not CoR.

On 2/16/06, Frank W. Zammetti <fzlists@omnytex.com> wrote:
>
> Craig McClanahan wrote:
> > This pattern, of course, can be used today in a Struts 1.x action ... o=
r
> in
> > the "action" equivalent of any other framework too (JSF, WebWork,
> > whatever).  And, it's not even web specific ... you can design your
> whole
> > business logic layer out of chains.
>
> Having done this recently in a behavioral analysis application that was
> not web-based, I know exactly what your saying.  I can't tell you how
> thrilled the business was in a meeting a few weeks ago when they said
> "well, what happens when we want to add a rule between C and D in this
> processing flow" and I was able to do it in about 1 minute right before
> their eyes.  They flipped!  CoR makes that flexibility very easy to do.
>
> > Craig
>
> Frank
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>


--
"You can lead a horse to water but you cannot make it float on its back."
~Dakota Jack~

------=_Part_1011_2745832.1140328688880--