You caught me ! That has actually already been fixed in the more recent 4.1.1-SNAPSHOT versions (ie not deprecated), but now that you've seen it I should probably explain what I attempted, but then reverted.
The original idea was that I've seen a lot of people get very frustrated when using the "listener" parameter of the Submit/similar components when they really should have been using the action parameter. (Both call a listener method - one does it as soon as possible, sometimes even before all of the form components have had their input gathered - and the other does it after the form has had a chance to grab all the incoming data.) The general idea was that I don't like the behaviour of listener="" overly much at all. I was going to try and sneakily replace the implementation of it with the logic that handles action="" but it was brought up that this would break some important logic in other components. I haven't given up on my quest yet, hopefully when normal 4.1 stabilization things get more settled I can make another attempt in 4.2 that is more thought out. On 8/1/06, Mark Reynolds <[EMAIL PROTECTED]> wrote:
Jesse, The "action" parameter on the Submit component is marked as deprecated, but with no explanation. Can you give us the low down? Thanks. -- Mark R --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Jesse Kuhnert Tacos/Tapestry, team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind.