Re: Editor Framework: Client side validation and error handling
Found a solution to 1): I put the validation annotations in a separate interface that is implemented by both the proxy interface (client) and the domain class (server). Since the validation annotations will automatically be passed down the inheritance hierarchy, validation works now on the client as well as on the server. For a longer description with example see my reply to How to do client side validation with annotated rules on domain classes (RequestFactory)http://stackoverflow.com/a/10659828/862411 . - Marco -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/tt85P2AMliIJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Editor Framework: Client side validation and error handling
I'm also looking for a solution for 1). Is it possible to get validation from my domain classes on my proxy classes? How should I do with Editors? Thanks. Em segunda-feira, 17 de outubro de 2011 10h10min52s UTC-2, Jens escreveu: Hi, currently exploring the editor framework and client side validation and have some questions: 1.) As I use RequestFactory and server side validation is it a good idea to implement client side validation as well? The only benefits I can think of is immediate error feedback to the user without waiting for a server response. But on the other side I have to add all my validation annotations to my proxies again, right? Or is there a way to reuse the annotation information on server domain classes for proxies? I think in most cases validation annotations would not differ between server and client. 2.) If I want to integrate client side validation do I have to start the validation process on my own or is there any editor framework class that I do not have found yet that already integrates client side validation? If I have to start the process on my own are there any major drawbacks when integrating validation in a custom editor driver? Seems to be the cleanest solution, but of course I could also just use a small utility class/method that does flush + validate + report errors (which would definitely be faster to implement). 3.) When I receive validation errors I have to implement HasEditorErrors on all my views/editors in order to get notified about the error. Is it better to implement HasEditorErrors in the parent view and let the parent view display the errors for its child editors or is it better to code some wrapper widgets like ValueBoxEditorDecorator and let each child display its error on its own? For example you could have an error in person.name and now the person.name editor could show the error on its own or let the person view display the error (for example in a dedicated, combined errors area for the whole person view). Are there any practically differences between these two solutions? -- J. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/6296p5TcWdoJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Editor Framework: Client side validation and error handling
Hi, currently exploring the editor framework and client side validation and have some questions: 1.) As I use RequestFactory and server side validation is it a good idea to implement client side validation as well? The only benefits I can think of is immediate error feedback to the user without waiting for a server response. But on the other side I have to add all my validation annotations to my proxies again, right? Or is there a way to reuse the annotation information on server domain classes for proxies? I think in most cases validation annotations would not differ between server and client. 2.) If I want to integrate client side validation do I have to start the validation process on my own or is there any editor framework class that I do not have found yet that already integrates client side validation? If I have to start the process on my own are there any major drawbacks when integrating validation in a custom editor driver? Seems to be the cleanest solution, but of course I could also just use a small utility class/method that does flush + validate + report errors (which would definitely be faster to implement). 3.) When I receive validation errors I have to implement HasEditorErrors on all my views/editors in order to get notified about the error. Is it better to implement HasEditorErrors in the parent view and let the parent view display the errors for its child editors or is it better to code some wrapper widgets like ValueBoxEditorDecorator and let each child display its error on its own? For example you could have an error in person.name and now the person.name editor could show the error on its own or let the person view display the error (for example in a dedicated, combined errors area for the whole person view). Are there any practically differences between these two solutions? -- J. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/GWpvS2QVzygJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
