>I was thinking that anopther method, like execute() could just throw >exception and be called by the ActionServlet, and the perform() form >would not be called at all. So, like, deprecate perform() in favor of >execute() (or something), if we can get the controller to gracefully >choose between them. But I'm not sure how that would work ;-)
what about introducing of additional configuration parameter for ActionServlet in web.xml like: <init-param> <param-name>perform</param-name> <param-value>true</param-value> </init-param> which should be set by all legacy applications and would cause perform() to be executed. Otherwise - execute(). Dmitri Valdin -- Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>