If you're not opposed to using 1.2 the MappingDispatchAction will allow
you to easily set up multiple action mappings, each capable of having
their own ActionForm, validation, etc and then actually handle these all
with a multiple methods in a single Action class.
http://jakarta.apache.org/st
Sorry about that link. Frames are a killer ...
http://jakarta.apache.org/struts/api/org/apache/struts/actions/MappingDispatchAction.html
Mike Foody wrote:
If you're not opposed to using 1.2 the MappingDispatchAction will
allow you to easily set up multiple action mappings, each capab
method, why not just
skip the dispatch aciton altogether and have separate actions? If you
keep all related actions in a package together, is it any harder to
manage? I am talking about having a configuration like this:
Mike F
3 matches
Mail list logo