Many thanks for your comments. My replies below:
(SNIP) > 1) Be able to bind a user request to an arbitrary function > in an Action class, not just to perform(). > > 2) Be able to bind each button in a form with multiple submit > buttons to an arbitrary function (such that control is > transferred to a specific functions based on which button > was clicked). > Doesn't the mechanism of the existing DispatchAction cover these? Yes and no. Item 2) is not addressed in Struts 1.0 at all, although in Struts 1.1 there now is LookupDispatchAction. However, as I pointed out in my original posting, I am unhappy with making the actual names of my methods visible on the client. I also would like a different mechanism than introducing additional request parameters: after all, it is not the request that gets dispatched, but the action! > 3) Provide the ability to restrict access to actions as part > of the configuration (ie in struts-config.xml). > Doesn't the combination of container-managed security and <action role=".."> cover this? Good point, but you may not be able to or do not want to use container managed security. > 4) Reduce the number of runtime String lookups (such as when > writing: mapping.findForward( "success" ) ). > Are you worried about performance? No, runtime-errors. As I described later in the posting, String-lookups are not checked by the compiler, and therefore only fail at runtime (ie functional testing), which is inconvenient. > > Philipp K. Janert, Ph.D. janert at ieee dot org > -- John Yu Scioworks Technologies e: [EMAIL PROTECTED] w: +(65) 873 5989 w: http://www.scioworks.com m: +(65) 9782 9610 Scioworks Camino - "Don't develop Struts Apps without it!" -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
