myfaces

I am trying to override the default validateDateTimeRange message using messageDetailNotInRange as per the documentation. Despite my code, the validator produces the default error message: "The date is outside the valid range." Can anyone see something wrong here? <tr:inputDate required="true" inlineStyle="color:rgb(0,58,117); font-weight:bold;" value="#{processScope.benefit.serviceDate}" immediate="false" onchange="submit();" label="#{mb_ResourceBean.res['claim.serviceDate.label']}"> <tr:convertDateTime pattern="yyyy/MM/dd" secondaryPattern="yyyyMMdd" type="date"/> <tr:validateDateTimeRange

I have 2 basic templates - one with a side menu, and one without - that both ui:include a common page which contains ui:insert tags (templates are largish, so basic example below). Using Mojarra everything worked ok, but now I have migrated to MyFaces the ui:insert tags are ignored and the content of the related ui:define does not get rendered (i.e. 'Here are my results' is not displayed). Should I be specifying included-page.xhtml as a template somehow? I tried <ui:composition template="included-page.xhtml" /> instead of <ui:include src="included-page.xhtml" /> but lost the CSS. Hoping

I am trying to create a simple JSF web application using MyFaces v 2.1 with WebSphere Application Server Community Edition v3.0.0.1 and Eclipse Juno but when I try to run the application the following error is returned java.lang.ClassNotFoundException: com.sun.faces.config.ConfigureListener org.apache.geronimo.common.DeploymentException: java.lang.ClassNotFoundException: com.sun.faces.config.ConfigureListener at org.apache.geronimo.web25.deployment.AbstractWebModuleBuilder.createWebAppClassFinder(AbstractWebModuleBuilder.java:665) at org.apache.geronimo.web25.deployment

In JSF, there is a viewstate associated with each page, which is passed back and forth with submits etc. I know that viewstate is calculated using the states of the various controls on the page, and that you can store it either client side or server side. The question is: how is this value used? Is it used to validate the values sent at submit, to ensure that the same request is not sent twice? Also, how is it calculated - I realise that richfaces may be calculated differently from myfaces, but an idea would be nice. Thanks. The question is: how is this value used? Is it used to validate the

We are migrating JSF 1.1 (MyFaces) project to JSF 2. The idea is to migrate periodically by keeping both JSP and XHTML together for some time. We use many ajax4jsf-1.1.1 tags in JSP pages. We don't use RichFaces. After configuring the system to JSF 2 (with all config changes mentioned in tutorial by Balusc) When tried to access the JSP page with ajax4jsf.jar in classpath, we get an exception: Caused by: java.lang.IllegalStateException: setViewHandler may not be executed after a lifecycle request has been completed at org.apache.myfaces.application.ApplicationImpl.setViewHandler(ApplicationImpl

It seems that today (April 2012), both MyFaces and Mojarra's JSF 2.1 implementations have defects around partial state saving and that PARTIAL_STATE_SAVING should be set to false. Is this true? BalusC Should PARTIAL_STATE_SAVING be set to false? Only when you encounter a general defect related to partial state saving in your webapp which can really not be solved/workarounded the other way. Partial state saving has namely major advantages as to overall performance and memory usage. See also Why JSF saves the state of UI components on server? I can't 100% reliably speak for MyFaces, but in