Following up on some other threads, here's some things we might consider for a future release
* Attaching a ViewHelper to an ActionForward. ** The ViewHelper (aka ViewController, aka ProxyAction, aka SetupGizmo) would be able to access the contexts before the ActionForward fires. It would *not* be able to select a different ActionForward on its own, but it *would* be able to throw an Exception that could be caught by the declarative ExceptionHandler. (Perhaps as a Filter?) ** The sticky part here is that we would like to separate the concern, but we also need to handle any errors that might occur when addressing the concern. We need to be clear that it is the Action's role to select the next view -- not the ViewController. ** Other names for this component might be ViewProxy, PageProxy, or PageDelegate * Easy ActionForm instantiation. ** An Action or ViewHelper should be able to easily instantiate an ActionForm given only the logical name of an Action or ActionForward. * Dynamic target for html:form. ** It's often useful to retarget a form for a different mapping. We should be able to set an attribute that will target an html:form for another mapping. This can be done with RTE, but it's messy. ** There was an old ticket for a taglib enhancement that would let us "back" all the attributes with a JavaBean. There was a cold reception at the time, but I keep thinking it might be a good way to pass in whateverr attributes people might need without resorting to RTEs ** An IOC container might be helpful if implemeting a taglib backing bean.. -Ted. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
