Hi you are having submit button in your component and you say component is created because some code has to be repeatedly used.
I had never faced this situation but a simple solution is except submit button create the other part as component and see.... Muralidhar Y Software Engineer, Adastrum technologies-Nikai groups, EmiratesGroup-I.T Division, Dubai, UAE. Mobile : 00971-50-2256149. http://www.adastrumtech.com http://www.mercator.aero (Keep Smiling. Be happy All The Time.) -----Original Message----- From: Alan Chandler [mailto:[EMAIL PROTECTED] Sent: 17 October 2005 14:26 To: [email protected] Subject: Problem with a submit button I have a situation in which one of my pages contains a form, and several submit buttons (with the @Submit component). They all use tag= and selected= to mark via a routine in this pages java class to indicate they have been pressed when the forms listener is executed. They work fine. I also have a component on the form (basically because some part is repeated with almost the same data) which also has a submit button in it so that it effectively is embedded with the same form. As soon as I hit this button, I get immediately sent to my applications home page - no messages, or anything. I have tried setting this components button with a tag="ognl:tagValue" so that the components java can establish a value and with selected="ognl:page.buttonClicked" so that the same routine as the buttons on the actual page record the value. I even tried changing that to be a routine in the component itself (ie selected="ognl:buttonClicked") so it could locally call getPage(). I have also tried setting up an action= listener on the button to call a routine in the components java class. In EVERY case putting breakpoints on all possible places (the routine to get the tag value the various selected routines and the listeners for the page level form and the component listener for the button I never hit ANY breakpoint and immediatly see the home page displayed. Is Tapestry calling some form of restart because of a problem? So I am stuck as to what is going wrong. Maybe it has to to with rewinding the form or something - but I can't see how to debug it. Has anyone else seen this problem? Is this a restart that is happening? Any ideas on how to debug to get more information on it? -- Alan Chandler [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
