Hi, After asking some questions on this list, I implemented a link that triggers an action, like a button. I used the method where the link triggers the action through parameters. Here is the html for the link:
<a href="http://localhost:8080/jetspeed/portal/media-type/html/user/anon/page/d efault.psml?formbutton_edit=Bewerken&bitformname=CVForm&buttonparameter_deta ilindex=0>Bewerken</a> The link carries three parameters, formbutton_edit, bitformname and buttonparameter_detailindex. I use the first two to determine that a formbutton (a LinkButton in this case) was pressed and which one, and to determine which form the button was on. The third parameter is a buttonparameter, of which 0 to n may be passed. Anyway, I implemented my own overridden version of org.apache.jetspeed.modules.actions.portlets.PortletActionEvent.executeEvent s(RunData data, Context context) in my portletaction, which checks for keys in the parameter map starting with 'formbutton_', before letting the parent look for 'eventSubmit_'. I tested it and it worked great, or at least seemed to. For some reason, if I press my LinkButton, and then one of the normal ones, the ParameterParser contains all my form values (the normal button submits the form, the link button is used as edit button in a master-detail view), but it ALSO contains all the link parameters from the time I pressed the link button... I have added lots of logging, and the RunData object I get in executeEvents() after the normal button is pressed, is still the same object as when the linkbutton was pressed. My questions: - Is the RunData object normally kept alive over multiple page requests? - Which class is responsible for clearing the parameters and which for filling them? - Has anyone seen this kind of behaviour before? Thanks for any help, -Stijn --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
