To the end of making it accessible to newcomers, what about making a "samples" directory for actions? Maybe even forms?
On Fri, 2003-08-01 at 06:19, Ted Husted wrote: > I use many utilities Actions like these, and the result is that fewer > *custom* Actions are needed. I think increasing the number of standard > Actions in the distribution is a very good idea. It makes Struts more > accessible to newcomers, saves everyone from reimplementing the same > design, and leverages the fact that Actions are singletons. > > -Ted. > > Vic Cekvenich wrote: > > I think less actions are needed, not more. > > .V > > > > Steve Raeburn wrote: > > > >> I'd like to add two new actions to org.apache.struts.actions that I find > >> particularly useful. > >> > >> 1. SuccessAction - A simple action that forwards control to an > >> ActionFoward > >> named "success". > >> > >> This is a very simple action, but I find it exceptionally useful, > >> particularly in the early stages of development when it can act as a > >> placeholder for as-yet undeveloped actions. > >> > >> public ActionForward execute( > >> ActionMapping mapping, > >> ActionForm form, > >> HttpServletRequest request, > >> HttpServletResponse response) > >> throws Exception { > >> > >> ActionForward forward = mapping.findForward("success"); > >> if (forward == null) { > >> String message = > >> messages.getMessage("success.required", mapping.getPath()); > >> log.error(message); > >> throw new ServletException(message); > >> } > >> return forward; > >> } > >> > >> 2. ParameterDispatchAction - A DispatchAction that selects a handler > >> method > >> using the value of the ActionMapping parameter. > >> > >> This is as per the suggestion by Anthony Kay via Bugzilla > >> <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17117>, except I > >> prefer > >> the name ParameterDispatchAction to his suggestion of > >> ConfigDispatchAction > >> as I think it's more descriptive of what the class actually does. > >> Other than > >> the name change, I've just tidied up the Javadoc and changed the > >> 'unspecified' method to throw an Exception (as in DispatchAction) rather > >> than return an Http error code. > >> > >> If no one has any problems with adding these two, I'll put them in > >> tomorrow. > >> > >> > >> Steve > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > -- Benjamin Tomasini <[EMAIL PROTECTED]> NetEverything, Inc. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]