Add faces message without valuebinding

Question

I have a mandatory input field and I don't want use the required attribute to force the user to fill it.
I would like attach a converter just to convert an input value only if it was entered and validate the input "requireness" using an action method in my backbean.
I know that I can do this:
FacesContext facesContext = FacesContext.getCurrentInstance();
facesContext.addMessage(<optionalRelatedComponentReference>.getClientId(facesContext),
                   new FacesMessage(FacesMessage.SEVERITY_<WHATEVER>,
                       "<messageSummary>", "<messageDetail>"));but I don't want to make a valuebinding to get the client id for every mandatory input (I have several input fields!).
How can I solve?
Thank you.

Answer 1

alf.redo wrote:
I have a scenario with multiple pages (like tabs), each one include the same submit button. Every page collects inserted data into page-related session beans.
The user can browse the pages and press the common submit button from any page.
I need that the user can browse all pages and only when the common sumbit button is clicked do the check for mandatory fields so he can browse from one page to another also if he not entered a value at all.
I want also that he can't leave a page if he entered invalid values (easy with standard convertion architecture).So each tab switch costs one POST request to the server and you want to save all form values without any validation? Have you considered client side tabbing (JS+DOM)?
I can't check for the submit button in the request scope to set the value of the required attribute because in this way I check only for the current page.You can do a conditional check in EL.required="#{page1submitted || page2submitted || page3submitted}"You can also get it as a bean property which checks the ExternalContext#getRequestParameterMap().
The only componet binding I know is through the "binding" attribute, but I don't want to specify a component binding in my backbean for each mandatory input :-(
I missed something?You want the client ID of the component. The only way to get it is to get it from the bound component, or to hardcode the client ID somewhere that the code can access it.