posted 14 years ago
If you throw an exception , i believe you get a stack trace, so you need to clear the "java" error log, not just handle it and take what you want in either "summary" or "the full report".
If you use SAX or DOM with Xerces , the process of document validation is handled the same way for the point, so you can grab a complete stack trace that is logged. Though you can probably switch off logging for that component or section relating the Exception if you want and that would make that more sensible for using an exception.
Just thought i'd add this since my last post was a bit rough in its explaination:
But if memory serves me correctly it's only required to have the for= part bound to the component.
When a component is validated in a validator, if it is set unvalid and an h:outputmessage is associated to the components id by a for="thevalidatedcomponentsID" , the error message queued on the component will show , there is no need to change the render attribute of the h:outputmessage .
...did you have the fish?!............................ No.