^ pop-out codeShare ^
  1. <cfif isDefined ( 'form.fieldNames' )>
  2. <!---
  3. This variable will collect errors.
  4. The form display will iterate over
  5. the array and display any errors
  6. that exist.
  7. --->
  8. <cfset variables.errors = arrayNew(1) />
  10. <cftry>
  11. <!---
  12. Field validation
  13. It's extremely annoying to show
  14. users one validation error message
  15. at a time. These should be collected
  16. and displayed en masse.
  17. --->
  18. <cfif [some field is not valid]>
  19. <cfset arrayAppend ( variables.errors, 'Invalid value message' ) />
  20. </cfif>
  21. <cfif [some other field is not valid]>
  22. <cfset arrayAppend ( variables.errors, 'Invalid value message' ) />
  23. </cfif>
  24. <cfif arrayLen ( variables.errors ) gt 0>
  25. <!---
  26. The throw will bypass any further
  27. processing without the need for an
  28. extended cfif block around all of
  29. that additional processing.
  30. --->
  31. <cfthrow type="validation" />
  32. </cfif>
  33. ... start processing ...
  34.     
  35. <!---
  36. Some processing needs to be isolated
  37. for specific error handling. Errors
  38. can be rethrown to the primary handler
  39. to skip further processing.
  40. --->
  41. <cftry>
  42. ... isolated processing ...
  43.         
  44. <cfcatch type="any">
  45. <cfrethrow />
  46. </cfcatch>
  47. </cftry>
  48.     
  49. ... continue processing ...
  51. <cfcatch type="validation">
  52. <!---
  53. Errors sent here are already in
  54. the errors array and can just be
  55. allowed drop to the form view for
  56. display.
  57. --->
  58. </cfcatch>
  59. <cfcatch type="any">
  60. <!---
  61. In the simplest cfcatch scenario,
  62. the error message can just be
  63. appended to the errors array.
  64. --->
  65. <cfset arrayAppend ( variables.errors, cfcatch.message ) />
  66. </cfcatch>
  67. </cftry>
  68. </cfif>