struts-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin Cooper <mart...@apache.org>
Subject Re: Reasons for 1.3 release
Date Thu, 16 Feb 2006 23:08:27 GMT
On 2/16/06, Paul Benedict <paul4christ79@yahoo.com> wrote:
>
> >>I think CoR is a great pattern, I've used it with great success, but I'm
> not as sure how it fits into Struts *outside* the composable RP, which is
> a *perfect* application for it.  Just curious how you (and/or others) are
> already using it.
>
> This is my opinion too. I think the CoR is made for the Struts internal
> processing only but some
> people are testing it out, as Ted said and Martin admitted to, as an end
> point for action
> processing.
> From my perspective, it's clear what the intention of CoR is by its design
> and use, but since it
> was never explicitly spelled out how it is used in Struts, I have to defer
> to other opinions too.
> But unless I am wrong, I think it's strongly geared towards the RP and not
> actions.


In Struts 1.3, you can do:

    <action path="/MyAction"
            catalog="MyCatalog"
            command="MyCommand"/>

or, if you use the default catalog, as I do for my mappings:

    <action path="/MyAction"
            command="MyCommand"/>

I'd say that's geared towards actions.

--
Martin Cooper


That's why I said, ActionContext should be InternalActionContext. If Struts
> 1.4+ is going to have
> actions without a subclass or interface, you want a method signature like:
> public void
> execute(ActionContext cxt);
>
> Paul
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message