Hi,

 

My teammate and I have looked through the message archives (and
different web sites) and not been able to find a thread/site that
discusses how to handle this situation.

 

We are developing a web-app with multiple editors, each of which has a
Selection page where the user decides to Create, Read, Update, or View
the object supported by that editor.  Each Action Class handles the CRUD
functions for one object type and sub-classes LookupDispatchAction.  We
are constructing the pages using the Tiles framework.

 

Now the fun part:  We are implementing Validator.  The client-side
validation (javascript) works fine, but we have an issue with the
server-side validation.  When the validation fails, we should return to
the page that had the error.  I.E. When the user is creating and has a
server-side validation error, we need to return to the create page,
which is a tiles definition.similarly with the Update function, we need
to return to the update tiles definition.

 

The input tag in the action-mapping seems to be the answer, but it would
require multiple action mappings to have an input tag for each of the
tiles-mappings that used validator.

 

My question:  Is the input tag and multiple-action mappings the right
way to accomplish our goals?  The use of multiple action-mappings seems
messy; is there a better way?

 

Thanks for any advice or thoughts.

Nick

Reply via email to