Re: html:cancel doesn't perform as advertised
The javascript will be output by the html:form tag and it stops javascript validation. The cancel button should look like this: input type=submit name=org.apache.struts.taglib.html.CANCEL value=Cancel onclick=bCancel=true; / The JSP should look like this: html:cancelCancel or whatever/html:cancel Adam On 03/14/2004 12:56 AM Dean A. Hoover wrote: I have an html:form with a html:submit and an html:cancel. According to the documentation for html:cancel: Pressing of this submit button causes the action servlet to bypass calling the associated form bean validate() method. I tried it and it did validation anyway. Then I looked at the generated HTML and I see: input type=submit name=method value=Next input type=submit name=method value=Cancel onclick=bCancel=true; The only difference I see is the onclick attribute. How is that supposed to do anything, given that that there isn't any javascript in the file. What am I missing here? Dean Hoover - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- struts 1.1 + tomcat 5.0.16 + java 1.4.2 Linux 2.4.20 Debian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: html:cancel doesn't perform as advertised
What about the non-Javascript validation?... that's what I want to avoid. The whole Javascript validation thing is optional anyway and doesn't seem like the best way to implement it (because its optional). Dean Adam Hardy wrote: The javascript will be output by the html:form tag and it stops javascript validation. The cancel button should look like this: input type=submit name=org.apache.struts.taglib.html.CANCEL value=Cancel onclick=bCancel=true; / The JSP should look like this: html:cancelCancel or whatever/html:cancel Adam On 03/14/2004 12:56 AM Dean A. Hoover wrote: I have an html:form with a html:submit and an html:cancel. According to the documentation for html:cancel: Pressing of this submit button causes the action servlet to bypass calling the associated form bean validate() method. I tried it and it did validation anyway. Then I looked at the generated HTML and I see: input type=submit name=method value=Next input type=submit name=method value=Cancel onclick=bCancel=true; The only difference I see is the onclick attribute. How is that supposed to do anything, given that that there isn't any javascript in the file. What am I missing here? Dean Hoover - 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]
Re: html:cancel doesn't perform as advertised
Server-side validation is skipped by struts when it sees the org.apache.struts.taglib.html.CANCEL request param. On 03/14/2004 12:20 PM Dean A. Hoover wrote: What about the non-Javascript validation?... that's what I want to avoid. The whole Javascript validation thing is optional anyway and doesn't seem like the best way to implement it (because its optional). Dean Adam Hardy wrote: The javascript will be output by the html:form tag and it stops javascript validation. The cancel button should look like this: input type=submit name=org.apache.struts.taglib.html.CANCEL value=Cancel onclick=bCancel=true; / The JSP should look like this: html:cancelCancel or whatever/html:cancel Adam On 03/14/2004 12:56 AM Dean A. Hoover wrote: I have an html:form with a html:submit and an html:cancel. According to the documentation for html:cancel: Pressing of this submit button causes the action servlet to bypass calling the associated form bean validate() method. I tried it and it did validation anyway. Then I looked at the generated HTML and I see: input type=submit name=method value=Next input type=submit name=method value=Cancel onclick=bCancel=true; The only difference I see is the onclick attribute. How is that supposed to do anything, given that that there isn't any javascript in the file. What am I missing here? Dean Hoover - 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] -- struts 1.1 + tomcat 5.0.16 + java 1.4.2 Linux 2.4.20 Debian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: html:cancel doesn't perform as advertised
Adam, OK, I get that part now... I mistakenly changed html:submit property=methodbean:message key=button.cancel//html:submit to html:cancel property=methodbean:message key=button.cancel//html:cancel which turns into input type=submit name=method value=Cancel onclick=bCancel=true; instead of what you showed me: input type=submit name=org.apache.struts.taglib.html.CANCEL value=Cancel onclick=bCancel=true; / That breaks another part now... I created a subclass of LookupDispatchAction to handle the various button presses. If the user clicks on the Cancel button I just want to take my cancel forward. What do I need to do to my Action to accomplish that? Dean Hoover Adam Hardy wrote: Server-side validation is skipped by struts when it sees the org.apache.struts.taglib.html.CANCEL request param. On 03/14/2004 12:20 PM Dean A. Hoover wrote: What about the non-Javascript validation?... that's what I want to avoid. The whole Javascript validation thing is optional anyway and doesn't seem like the best way to implement it (because its optional). Dean Adam Hardy wrote: The javascript will be output by the html:form tag and it stops javascript validation. The cancel button should look like this: input type=submit name=org.apache.struts.taglib.html.CANCEL value=Cancel onclick=bCancel=true; / The JSP should look like this: html:cancelCancel or whatever/html:cancel Adam On 03/14/2004 12:56 AM Dean A. Hoover wrote: I have an html:form with a html:submit and an html:cancel. According to the documentation for html:cancel: Pressing of this submit button causes the action servlet to bypass calling the associated form bean validate() method. I tried it and it did validation anyway. Then I looked at the generated HTML and I see: input type=submit name=method value=Next input type=submit name=method value=Cancel onclick=bCancel=true; The only difference I see is the onclick attribute. How is that supposed to do anything, given that that there isn't any javascript in the file. What am I missing here? Dean Hoover - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: html:cancel doesn't perform as advertised
Hi Dean, I'm not sure what you're doing in your LookupDispatchAction, so I can't really say. I'm not too hot on DispatchActions. Isn't there a default? Or some other way that DispatchAction handles cancels? Adam On 03/14/2004 03:34 PM Dean A. Hoover wrote: Adam, OK, I get that part now... I mistakenly changed html:submit property=methodbean:message key=button.cancel//html:submit to html:cancel property=methodbean:message key=button.cancel//html:cancel which turns into input type=submit name=method value=Cancel onclick=bCancel=true; instead of what you showed me: input type=submit name=org.apache.struts.taglib.html.CANCEL value=Cancel onclick=bCancel=true; / That breaks another part now... I created a subclass of LookupDispatchAction to handle the various button presses. If the user clicks on the Cancel button I just want to take my cancel forward. What do I need to do to my Action to accomplish that? Dean Hoover Adam Hardy wrote: Server-side validation is skipped by struts when it sees the org.apache.struts.taglib.html.CANCEL request param. On 03/14/2004 12:20 PM Dean A. Hoover wrote: What about the non-Javascript validation?... that's what I want to avoid. The whole Javascript validation thing is optional anyway and doesn't seem like the best way to implement it (because its optional). Dean Adam Hardy wrote: The javascript will be output by the html:form tag and it stops javascript validation. The cancel button should look like this: input type=submit name=org.apache.struts.taglib.html.CANCEL value=Cancel onclick=bCancel=true; / The JSP should look like this: html:cancelCancel or whatever/html:cancel Adam On 03/14/2004 12:56 AM Dean A. Hoover wrote: I have an html:form with a html:submit and an html:cancel. According to the documentation for html:cancel: Pressing of this submit button causes the action servlet to bypass calling the associated form bean validate() method. I tried it and it did validation anyway. Then I looked at the generated HTML and I see: input type=submit name=method value=Next input type=submit name=method value=Cancel onclick=bCancel=true; The only difference I see is the onclick attribute. How is that supposed to do anything, given that that there isn't any javascript in the file. What am I missing here? Dean Hoover - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- struts 1.1 + tomcat 5.0.16 + java 1.4.2 Linux 2.4.20 Debian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
html:cancel doesn't perform as advertised
I have an html:form with a html:submit and an html:cancel. According to the documentation for html:cancel: Pressing of this submit button causes the action servlet to bypass calling the associated form bean validate() method. I tried it and it did validation anyway. Then I looked at the generated HTML and I see: input type=submit name=method value=Next input type=submit name=method value=Cancel onclick=bCancel=true; The only difference I see is the onclick attribute. How is that supposed to do anything, given that that there isn't any javascript in the file. What am I missing here? Dean Hoover - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: html:cancel
Not as such. What you can do is have the Action class look for a a cancel forward when there is a cancelled command. This lets you define a local cancel forward when needed or rely on a global one otherwise. HTH, Ted. Gandle, Panchasheel wrote: Is there a way to go back to previous, previous page without having a extra forward in the config file. say I'm on list page then I go to add page which calls pageAddAction on cancel I want to go back to list page and not on pageAdd when users cancel it. action pageAdd input list action pageAddAction input pageAdd Thanks Panchasheel -- Ted Husted, Junit in Action - http://www.manning.com/massol/, Struts in Action - http://husted.com/struts/book.html, JSP Site Design - http://www.amazon.com/exec/obidos/ISBN=1861005512. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
html:cancel
Is there a way to go back to previous, previous page without having a extra forward in the config file. say I'm on list page then I go to add page which calls pageAddAction on cancel I want to go back to list page and not on pageAdd when users cancel it. action pageAdd input list action pageAddAction input pageAdd Thanks Panchasheel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
html:reset and html:cancel
Is it just me, or do these objects have no intrinsic affect on html:text objects? Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: html:reset and html:cancel
On Tuesday 10 June 2003 14:30, Mark Galbreath wrote: Is it just me, or do these objects have no intrinsic affect on html:text objects? From which perspective do you mean? Client or server? The reset is basically an html input of type reset which will effect the page on the client side, while the cancel submit the form, but signals the controller that the form was cancelled (server side). I doubt you suffer from this, but I've seen several cases where developers think that if the user fills out a form and submits it, but it fails on validation and returns to render the page with those invalid entries, that hitting the reset will reset (in their mind) the page back to a blank page. That, of course, is the difference between a reset and a clear button. Have I come close to answering your question? Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- James Mitchell Software Developer/Struts Evangelist http://www.struts-atlanta.org 770-822-3359 AIM:jmitchtx - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: html:reset and html:cancel
Close - input type=reset/ and html:reset/ both clear input type=text/ but neither clear html:text/. Until Struts, I always used input type=reset/ to clear the textfields of a form and assumed html:reset/ would do the same. So my original question is, what intrinsic value does html:reset/ have for html:text/ objects if they cannot clear them or reset them to their default values on the client? RU saying that I have to create a custom clear() function to clear html:text/ objects on the client side (or is this even possible on the client)? Mark -Original Message- From: James Mitchell [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 10, 2003 2:51 PM To: Struts Users Mailing List Subject: Re: html:reset and html:cancel On Tuesday 10 June 2003 14:30, Mark Galbreath wrote: Is it just me, or do these objects have no intrinsic affect on html:text objects? From which perspective do you mean? Client or server? The reset is basically an html input of type reset which will effect the page on the client side, while the cancel submit the form, but signals the controller that the form was cancelled (server side). I doubt you suffer from this, but I've seen several cases where developers think that if the user fills out a form and submits it, but it fails on validation and returns to render the page with those invalid entries, that hitting the reset will reset (in their mind) the page back to a blank page. That, of course, is the difference betwee a reset and a clear button. Have I come close to answering your question? Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- James Mitchell Software Developer/Struts Evangelist http://www.struts-atlanta.org 770-822-3359 AIM:jmitchtx - 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]
Re: html:reset and html:cancel
On Tuesday 10 June 2003 15:00, Mark Galbreath wrote: Close - input type=reset/ and html:reset/ both clear input type=text/ but neither clear html:text/. Until Struts, I always used input type=reset/ to clear the textfields of a form and assumed html:reset/ would do the same. So my original question is, what intrinsic value does html:reset/ have for html:text/ objects if they cannot clear them or reset them to their default values on the client? RU saying that I have to create a custom clear() function to clear html:text/ objects on the client side (or is this even possible on the client)? Yes and no, when the page is rendered, the values you see are those input's default values, so hitting reset will change them back to their default values (values they had when the page was loaded). If this happens to be a new form (such as creating a new registration in the struts-example), then those fields are typically emtpy (exeption being default values that may have been used). From here, if you fill out the entire form, then hit reset, the fields will revert to their values that were there when the page was rendered. However, if you hit enter after filling out the form, but validation fails and you are brought back to the jsp to fill in...oh, let's say a required field that was left blank, then hitting reset at that point looks like it does nothing, hence the confusion. A clear can be implemented either on the client or the server (it's your choice). For client approach, you must do as you suggested (JavaScript, isn't it wonderful?). For a server-side clear, just use html:cancel but change it to show Reset (html:cancel value=Reset). Read up on the docos for this one. There are a couple of gotcha's. So, I hope this clears things up ;) Mark -Original Message- From: James Mitchell [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 10, 2003 2:51 PM To: Struts Users Mailing List Subject: Re: html:reset and html:cancel On Tuesday 10 June 2003 14:30, Mark Galbreath wrote: Is it just me, or do these objects have no intrinsic affect on html:text objects? From which perspective do you mean? Client or server? The reset is basically an html input of type reset which will effect the page on the client side, while the cancel submit the form, but signals the controller that the form was cancelled (server side). I doubt you suffer from this, but I've seen several cases where developers think that if the user fills out a form and submits it, but it fails on validation and returns to render the page with those invalid entries, that hitting the reset will reset (in their mind) the page back to a blank page. That, of course, is the difference betwee a reset and a clear button. Have I come close to answering your question? Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- James Mitchell Software Developer/Struts Evangelist http://www.struts-atlanta.org 770-822-3359 AIM:jmitchtx - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: html:reset and html:cancel
Using html:reset/ or html:cancel does not clear the entered data to defaults. This is before a submit, typically when a user has entered a bunch of data and realized he was looking at the wrong ledger and wants to reset everything to 0. It's not working. And this shouldn't be rocket science! :-) Mark -Original Message- From: James Mitchell [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 10, 2003 3:21 PM To: Struts Users Mailing List Subject: Re: html:reset and html:cancel On Tuesday 10 June 2003 15:00, Mark Galbreath wrote: Close - input type=reset/ and html:reset/ both clear input type=text/ but neither clear html:text/. Until Struts, I always used input type=reset/ to clear the textfields of a form and assumed html:reset/ would do the same. So my original question is, what intrinsic value does html:reset/ have for html:text/ objects if they cannot clear them or reset them to their default values on the client? RU saying that I have to create a custom clear() function to clear html:text/ objects on the client side (or is this even possible on the client)? Yes and no, when the page is rendered, the values you see are those input's default values, so hitting reset will change them back to their default values (values they had when the page was loaded). If this happens to be a new form (such as creating a new registration in the struts-example), then those fields are typically emtpy (exeption being default values that may have been used). From here, if you fill out the entire form, then hit reset, the fields will revert to their values that were there when the page was rendered. However, if you hit enter after filling out the form, but validation fails and you are brought back to the jsp to fill in...oh, let's say a required field that was left blank, then hitting reset at that point looks like it does nothing, hence the confusion. A clear can be implemented either on the client or the server (it's your choice). For client approach, you must do as you suggested (JavaScript, isn't it wonderful?). For a server-side clear, just use html:cancel but change it to show Reset (html:cancel value=Reset). Read up on the docos for this one. There are a couple of gotcha's. So, I hope this clears things up ;) Mark -Original Message- From: James Mitchell [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 10, 2003 2:51 PM To: Struts Users Mailing List Subject: Re: html:reset and html:cancel On Tuesday 10 June 2003 14:30, Mark Galbreath wrote: Is it just me, or do these objects have no intrinsic affect on html:text objects? From which perspective do you mean? Client or server? The reset is basically an html input of type reset which will effect the page on the client side, while the cancel submit the form, but signals the controller that the form was cancelled (server side). I doubt you suffer from this, but I've seen several cases where developers think that if the user fills out a form and submits it, but it fails on validation and returns to render the page with those invalid entries, that hitting the reset will reset (in their mind) the page back to a blank page. That, of course, is the difference betwee a reset and a clear button. Have I come close to answering your question? Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- James Mitchell Software Developer/Struts Evangelist http://www.struts-atlanta.org 770-822-3359 AIM:jmitchtx - 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]
html:cancel and LookupDispatchAction
Hi all, I have a LookupDispatchAction that my jsp is going to. I need to provide cancel functionality for this page. I tried to use the html:cancel but with the property on it, it still tries to perform the validation. I know its documented but is there a way around it? How do you skip validation and provide the cancel then for a LookupDispatchAction? Thanks, -Tim -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Hot to an html:image.. similar to html:cancel/ ?
Hi, I would like to use a image button (html:image..) instead of html:cancel/. How can I do that? It also fine of I have to handle that in the Action class. Zsolt -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
html:cancel problem
Hi, I have problem with the html:cancel tag in STRUTS 1.02 I have an Action class that create an instance of a ActionForm, populate it with data and put it in the session (session.setAttribute). Then my action class redirect the request to a JSP page that display the data from the sessions actionForm. The problem occur when someone modify one of the fields in the JSP and then click the cancel button. The data in the session has been modified event if thats a cancel button. Is it normal? Can someone help me with that? Thank you! Nicolas
html:cancel/
From everything that I can tell when using the html:cancel/ tag, my perform() method in my Action class never seems to get executed. It appears that after pressing the cancel button that the forward tag named as cancel in my action mapping in the struts-config file is used and forwards to the specified path, bypassing calling the perform() method. I understand that the validate() method in my form bean won't be called if the cancel button is pressed but I would think that my perform() in my Action class should be called. Is anyone else having a problem with this or am I misunderstanding something. Thanks for you help. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: html:cancel/
It turns out that on our project they are overriding several methods in the ActionServlet one of which changes the way the cancel button is handled. On Fri, 12 Jul 2002, Paul McKinney wrote: From everything that I can tell when using the html:cancel/ tag, my perform() method in my Action class never seems to get executed. It appears that after pressing the cancel button that the forward tag named as cancel in my action mapping in the struts-config file is used and forwards to the specified path, bypassing calling the perform() method. I understand that the validate() method in my form bean won't be called if the cancel button is pressed but I would think that my perform() in my Action class should be called. Is anyone else having a problem with this or am I misunderstanding something. Thanks for you help. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
How to achieve html:cancel but with an image?
Is there a way to achieve html:cancel characteristics with an input image? I'd like to call isCancelled() in my perform() method when a cancel image is pressed. Does the HTML tag library support that? Thanks, George Cutrell Technical Manager, Wireless Applications Development Nextel Communications, Inc. Desk: 703.433.8868 Mobile: 703.926.7851 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: How to achieve html:cancel but with an image?
html:image src=images/cancel.gif border=0 property=org.apache.struts.taglib.html.CANCEL/ -Original Message- From: Cutrell, George [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 09, 2002 4:45 PM To: 'Struts Users Mailing List' Subject: How to achieve html:cancel but with an image? Is there a way to achieve html:cancel characteristics with an input image? I'd like to call isCancelled() in my perform() method when a cancel image is pressed. Does the HTML tag library support that? Thanks, George Cutrell Technical Manager, Wireless Applications Development Nextel Communications, Inc. Desk: 703.433.8868 Mobile: 703.926.7851 -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED] -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
How to make html:cancel as an image?
Hi, Does anyone know how to associate an image with the html:cancel tag? Thanks. -Nimmi
