1. WARNING: FacesMessage(s) have been enqueued, but may not have been displayed. icefaces.orgpublic void validateInputSortgroupDescription(FacesContext context, UIComponent validate, Object value) { final LSB_JB_TraceInfoMethod tim = new LSB_JB_TraceInfoMethod( SSF_DI_JSF.METHODID_SSF_DI_SPDB_VALIDATEINPUTSORTGROUPDESCRIPTION, "validateInputSortgroupDescription"); LSB_JB_Trace.traceEntry(tic, tim, this.sessionID); String inputValue = (String) value; boolean isValid = true; if (inputValue.length() > SSF_DI_SPMLogicInterface.SORTGROUP_DESCRIPTION_COLUMN_MAXSIZE) { isValid = false; } ((UIInput) validate).setValid(isValid); if (isValid == false) { FacesMessage msg = new FacesMessage(FacesMessage.SEVERITY_ERROR, "The sortgroup description is too long (maximum " + SSF_DI_SPMLogicInterface.SORTGROUP_DESCRIPTION_COLUMN_MAXSIZE + ... |
2. Facesmessage appaear and disappear : is it ok how i do? icefaces.org |
4. FacesMessage(s) have been enqueued, but may not have been displayed. icefaces.orgHi, We are managing CRUD operation on a single page using Flags. In add mode we are displaying a List button on top that lists the records On clicking the List button, we are getting the following error messages INFO: WARNING: FacesMessage(s) have been enqueued, but may not have been displayed. sourceId=j_id78:name[severity=(ERROR 2), summary=(Employee Name: Validation Error: Value is required.), detail=(Employee ... |
5. INFO: WARNING: FacesMessage(s) have been enqueued, but may not have been displayed. icefaces.orgprivate static final String PHONE_NUM= "[0-9][0-9]-[0-9][0-9]-[0-9][0-9]-[0-9][0-9]"; public void teltxt_validate(FacesContext context, UIComponent component, Object value) { Pattern mtel = Pattern.compile(PHONE_NUM); String telnum = (String)value; Matcher matchtel = mtel.matcher(telnum); if (!(matchtel.matches())){ FacesMessage msg1 = new FacesMessage("Validar Formato Telefnico"); msg1.setDetail("El nmero de telfono no tiene el formato correcto"); msg1.setSummary("El nmero de telfono no tiene el formato correcto"); msg1.setSeverity(FacesMessage.SEVERITY_ERROR); context.addMessage(component.getClientId(context),msg1); //throw new ValidatorException(msg1); } } ... |
6. FacesMessage(s) warning icefaces.orgThe problem was because the id to which I am assigning the validation message was incorrect. It is working fine now after correction. The id actually gets appended with a string "j_id1" automatically. For ex: if the text field id is "name" then in the managed bean while assigning the error message we have to give the id as: context.addMessage("j_id1:form1:name", message); ... |
8. new FacesMessage() doesn't appear? icefaces.orgIn the method below, I create a new FacesMessage object which I populate then display on my .jspx page: private HtmlOutputText selItemsOutput; public void doFreeFormSearch(ActionEvent event) throws NamingException { FacesContext context = FacesContext.getCurrentInstance(); FacesMessage message = new FacesMessage(); if(getTransStartDate() == null && getTransEndDate() == null){ message.setSeverity(FacesMessage.SEVERITY_ERROR); message.setSummary("Input Error: Please select a start date and end date."); message.setDetail("Input Error: Please select a ... |
9. FacesMessage(s) have been enqueued, but may not have been displayed. icefaces.orgHi there! We have moved this morning our platform from IBM JDK 1.4.2 + JBoss 4.0.5 to IBM 1.5.0 + JBoss 4.2.1 (with JSF 1.2 instead of MyFaces 1.1). In the logs I notice quite frequent an info line which reads: INFO [javax.enterprise.resource.webcontainer.jsf.lifecycle] WARNING: FacesMessage(s) have been enqueued, but may not have been displayed. sourceId=null[severity=(FATAL 3), summary=(null), detail=(Autentificare esuata. Utilizator si ... |