I solved this by having a single form and generating dynamic radio buttons instead, and have a single submit at the bottom.
As to your strategy, the problem is that submit component does not pass context to select event so it's hard to pass in additional information. -adam On Tue, Apr 1, 2008 at 5:45 PM, Imants Firsts <[EMAIL PROTECTED]> wrote: > Hello! > > It is quite clear how to use this event if the > component is hardcoded in the template, you just use > onSelectedFromMySubmit() method in your component. > > Is it possible to handle onSelected event for > dynamically generated Submit components? I have a loop > which generates several Submit components. > > Basically what I want to achieve is the delete > functionality for list elements in the form. I have a > list of rendered entities with Delete buttons next to > each of them and I want to know on the server side, > which button was pressed. > > One of the alternatives is to use ActionLink, but I > really would not like to do that, because they send GET > request to the server instead of the POST. And I have > some kind of phobia from crawlers clicking my > ActionLinks. In this case the page is for authenticated > users only, but still... > > Thanks in advance, > Imants > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
