Hi,
In my opinion default method has to be used when the parameter is
specified but the value in the http request is not specified or it
doesn't correspond to a method defined in the action.
Can happen that developers need to collapse some method calls in the
default method call. So I don't think t
I'm against changing it in this way. Currently all three flavours of
DispatchAction require the parameter to be configured in the
struts-config.xml in order for them to be able to determine which method to
call. Without the parameter none of them can determine the method - thats a
different scenari
On 4/29/05, Michael Jouravlev <[EMAIL PROTECTED]> wrote:
> I think this is great and cheap solution. I would like DispatchAction
> to work like this. BTW, can non-committers comment on Struts changes?
Yes, but please be kind. :)
We're all working stiffs here, just like you, trying to do what we c
Hubert Rabago wrote:
Bugs 16104 and 34663 ask for a default method in DispatchAction. In
both cases, the response has been to use unspecified(). I think the
problem in both cases is the requirement for a mapping.getParameter()
value.
unspecified() only gets called if ActionMapping.parameter is pr
I think this is great and cheap solution. I would like DispatchAction
to work like this. BTW, can non-committers comment on Struts changes?
On 4/29/05, Hubert Rabago <[EMAIL PROTECTED]> wrote:
> Bugs 16104 and 34663 ask for a default method in DispatchAction. In
> both cases, the response has bee
