Jack,
You have said that LookupDispatchAction is outdated and inefficient. I
have at a minimum 6 different actions that need to be performed per page, not
including load. What else would you recommend as a solution?
Todd
-
Sorry, I seem to have spoken too soon. The method paramater will have a value
because the previous button has been pressed. I don't want to say we won't
validate on previous or next, since we need to, I just need to not validate if
struts is coming from another action
Thanks,
I had soemthing similar in my parent form LaserForm, but that just checked
for a query String on the request since we are bridging the old system to
struts. I just never made the connection to check for the method parameter.
Thanks for all the help.
Todd
Your first issue is a result of your second. The XML parser is telling you that
your format did not match the DTD. In the config, the elements must be in the
order of
1. data-sources
2. form-beans
3. global-forwards
4. action-mappings
5. messages and plugins.
for instance I have.
.
Hi all. I have a question that I cannot find the answer to, and hopefully
someone has run in to this.
I have 3 Actions and 2 Forms
AnnuityAction <-> AnnuityForm , BasicAction <-> BasicForm
I have an abstract class called LaserAction that extends LookupDispatchAction.
Both AnnuityAction and Ba
5 matches
Mail list logo
