+1 It's already in as ticket #13645
Personally, I think we should add this to the list on the release plan. It should have been int he API to begin with (like using ActionForward for inputs). My latest project uses Velocity templates, and the tools support doing this, so I am =:). I know find that as a result of using Actions in links, I no longer need to use as many ActionForwards, and the entire architechture is much cleaner and leaner. What happens is that instead of seeing ActionForwards as what we use to encapsulate links, you can come to view ActionMappings as what we use to ecapsulate forms -and- links. Since we can now enter a forward from an ActionMapping, everything else is already there. (And links are just streamlined GET forms anyway.) ActionForwards then become a workflow construct -- the outcome of an Action object, and nothing else. I think this was always the underlying intent of the architechture, but the missing html:link property clouded the issue. -Ted. 12/23/2002 9:37:39 PM, James Turner <[EMAIL PROTECTED]> wrote: >I find I write a lot of code that uses an intermediate action to >link between two web pages (this is good Struts policy in >general) However, since the html:link tag has a forward= but no >action=, I have to use page= and supply a URI with the ".do" >extension at the end, rather than being about to use action= as I >would with an html:form. What do folks think about adding >action= to html:link? > >James -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
