[ 
http://www.stripesframework.org/jira/browse/STS-737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11891#action_11891
 ] 

Yves Senn commented on STS-737:
-------------------------------

This would solve to forbidden jump problem but it would not solve everything. I 
think we should tell stripes the order of our eventHandlers in Wizard 
ActionBeans. This has multiple advantages:
- You can prevent the user from jumping inside the form. Stripes can make sure 
that the user passes the form exactly as the developer intended.
- You can allow "backward navigation" without validation errors. This problem 
is currently not solved and you have to make a workaround.
- The order of EventHandlers is also interesting for application logic. You 
will easily be able to create process bars and other navigation bars.


> Define EventHandler order for @Wizard ActionBeans
> -------------------------------------------------
>
>                 Key: STS-737
>                 URL: http://www.stripesframework.org/jira/browse/STS-737
>             Project: Stripes
>          Issue Type: New Feature
>          Components: Validation
>            Reporter: Yves Senn
>
> We have a multi-page form, that the user needs to fill step by step and 
> submit the order at the end. We currently use @Wizard for these kind of forms 
> and noticed that it is possible to just enter the data on the first page, 
> manipulate the name="" Attribute of the submit button and jump straight to 
> the last page. Stripes has no way of detecting that several form pages were 
> skipped since the field names never get written to the __fp hidden field.
> I think it should be possible to define an order for the eventHandlers. Then 
> stripes can make sure that the eventHandler for step3 gets called after 
> step2. With such a mechanism we can guarantee that the user has passed all 
> steps when he reaches the end of the wizard. I also think that it should be 
> possible to annotate an eventHandler to perform all validations and ignore 
> the values in __fp. This way we can make sure that risky actions like sending 
> an order or saving the record have all values present.
> To illustrate what I am thinking about I created an example Gist with the 
> eventHandler order: https://gist.github.com/1072357cbedbcbf0f587

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://www.stripesframework.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
_______________________________________________
Stripes-development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/stripes-development

Reply via email to