My memory on this is vague, but I suspect it's primarily an oversight.
Craig
On 4/20/05, Joe Germuska <[EMAIL PROTECTED]> wrote:
> I just happened to notice that there's a method on ActionMapping,
> "getInputForward()" which applies some config logic, while there's no
> corresponding method on ActionConfig. I could see where we might not
> directly reproduce it, since ActionConfig shouldn't depend on
> ActionForward -- but why is there method like
>
> public ForwardConfig getInputForwardConfig(){}
>
> which encapsulates the same logic?
>
> I can add it, but I thought I'd see if anyone had a good reason for
> leaving it out when ActionConfig was broken out from ActionForward?
>
> If it's a question of which classes know what, this is something
> which could probably be pushed into the ActionContext interface as
> well, but it is handy when one is doing validation inside an action.
> (In the chain, the logic is performed in AbstractSelectInput rather
> than calling on ActionMapping)
>
> Thanks
> Joe
>
> --
> Joe Germuska
> [EMAIL PROTECTED]
> http://blog.germuska.com
> "Narrow minds are weapons made for mass destruction" -The Ex
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
