[ 
https://issues.apache.org/struts/browse/SHALE-216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39924
 ] 

Veit Guna commented on SHALE-216:
---------------------------------

Got a workaround this. I just remove the token from the component tree when 
business validation fails and the form should be redisplayed. This seems to 
work for me. So now I can do business validations (action is called) after form 
validations and let the token be regenerated on business errors. It won't be 
handled as "submitted" anymore.

Is there another way to solve this?


> possibility to "skip" token validation when necessary
> -----------------------------------------------------
>
>                 Key: SHALE-216
>                 URL: https://issues.apache.org/struts/browse/SHALE-216
>             Project: Shale
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.0.3-SNAPSHOT
>         Environment: Myfaces 1.1.2
>            Reporter: Veit Guna
>             Fix For: TBD
>
>
> I'm using the shale token tag to avoid duplicate form submits. It works so 
> far.
> Now I have this usecase:
> - An input form is generated with fields for an address (street, areacode, 
> city etc.)
> - The token tag is placed in the bottom of the form to avoid re-submit
> - There are some validators in the form, that validate areacode in 
> combination with city
> - Is the city not unique when submitting, a warning msg is added to the 
> facescontext and the possible cities are presented in a selectbox to choose 
> from (javascript auto-submit)
> - After choosing the right city (the form is submitted automatically by JS), 
> another check looks for multiple areacodes for that city and displays them in 
> another selectbox with an additional msg in the facescontext that the user 
> has to select one.
> - When the user selects the areacode (JS auto-submit), the form is 
> re-displayed without any msg (because, everything is fine now)
> - Here is the problem: re-displaying the page without an queued error msg in 
> the facescontext will mark the form "as-sent".
> - So finally when the user wants to submit the form (after correcting his 
> input), the tag doesn't allow sending the form again.
> It would be nice, if it would be possible to "skip" a validation for the 
> token for re-displaying a page or to generate a new token when re-displaying 
> without
> validation errors.
> One "solution" would be to add an additional msg to the facescontext, when 
> validation of areacode+city is finally ok. But perhaps the component could 
> offer a solution to this?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to