See, I thought of going the same route, but I didn't want it to be the
burden of a task controller (Action). It just didn't seem to make sense at
that level, but I can see you struggled with the same uneasiness I did.
You're right, what we're both mimicking here is doGet and doPost of
HttpServlet
I use eventDispatcher. Default to present and others to submit.
http://wiki.apache.org/struts/DataEntryForm
someone post this url in this mailing list before.
El 24/05/2006, a las 20:01, Monkeyden escribió:
I recently came to the conclusion that I didn't like the hidden
form field
markers a
Monkeyden wrote:
> I'm wondering if anyone else has done something different and/or more
> practical.
Different, yes; more practical, probably not.
In the past I've just used a base Action class that differentiated
between GET and POST requests and called executeGet and executePost
methods. Inter
I recently came to the conclusion that I didn't like the hidden form field
markers and conditional logic used in the Action.execute() method, to
determine whether the user was performing the initial fetch of an
ActionMapping or submitting. The solution I came up with was to extend the
Struts Requ
4 matches
Mail list logo
