• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Multiple Form Validation Quest

 
Ranch Hand
Posts: 132
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi all,

on my pursue to attain highly maintainable validation requirements, I am wondering the following (using IceFaces):

in a page with a single form at the top of the component tree, I have several subsections, which are supposed to "validate" independently. On its half way I get it to behave like that. However I have a question: if I set for a section (panelGroup) the attribute rendered="false", the components in that section won't display (rendered=processed?), but they will still be pushed to the component validation queue. Is there by means of an attribute to avoid those components being handled by the lifecycle at all?, in order for the lifecycle to ommit validating them? This would importantly ease the task of including and leaving off sections to validate.

Thanks in advance,
Carlos Conti.
 
Power corrupts. Absolute power xxxxxxxxxxxxxxxx is kinda neat.
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic