mojarra

问题 In a JSF application, the parameter javax.faces.FACELETS_REFRESH_PERIOD can be used to enable/disable automatic reloading of XHTML files. I am currently researching the right configuration for production deployments, and accidentally found out that we currently run with FACELETS_REFRESH_PERIOD=1 even in production, which is obviously not a good idea. This lead to the question: What is the default value for this parameter? Ideally, I'd like to just omit FACELETS_REFRESH_PERIOD from our

问题 In a JSF application, the parameter javax.faces.FACELETS_REFRESH_PERIOD can be used to enable/disable automatic reloading of XHTML files. I am currently researching the right configuration for production deployments, and accidentally found out that we currently run with FACELETS_REFRESH_PERIOD=1 even in production, which is obviously not a good idea. This lead to the question: What is the default value for this parameter? Ideally, I'd like to just omit FACELETS_REFRESH_PERIOD from our

问题 Trying to implement the JSF 2.2 example I have the following code: <h:form prependId="false" enctype="multipart/form-data"> <!-- Now it's the AJAX file upload component --> <h:inputFile id="fileUpload" value="#{someBean.file}" > <f:ajax /> </h:inputFile> <h:commandButton value="Upload" /> </h:form> According to some JSF 2.2 this should work but in my case it is giving me the following error: the request doesn't contain a multipart/form-data or multipart/mixed stream, content type header is

问题 I have something like this on a create/edit form: <h:selectOneMenu value="#{bean.value}" required="true" ... > <f:selectItem itemLabel="-- Select --" itemValue=""/> <f:selectItems .../> </h:selectOneMenu> In the create new object case, the required validation works as expected. In the edit object case, if I change a valid value to the placeholder "-- Select --", I get the validation failure w/expected requiredMessage because itemValue is blank (""); however , the HTML <select> reverts to

问题 I am downloading Sun/Oracle Mojarra implementation of JSF from http://javaserverfaces.java.net/download.html I downloaded the latest -2.1.9 binary. It comes with only one jar - javax.faces-2.1.9.jar. I had a sample project which I believe is using the older 2.0 version, which includes 2 jars - jsf-api.jar and jsf-impl.jar. I replaced those 2 older jars with the single new jar. It seems like the sample project still works well. My question: Is there anything else I need to do besides replacing

问题 I am trying to deploy a web application in WebSphere 8.5. The app has the following characteristics. Mojarra 2.1.13 Primefaces 3.4.2 spring webflow 2.3.1 spring 3.1.2 jdk 1.6 This app works very well into Tomcat 7 but when we try to deploy it into WebSphere we got a NullPointerException with the following stacktrace. javax.faces.component.UIComponentBase.restoreDeltaSystemEventListenerClassMap(UIComponentBase.java:1933) javax.faces.component.UIComponentBase.restoreState(UIComponentBase.java

问题 On a WAS 7, I deployed my EAR with a single WAR in it. The EAR classloading mode is set to PARENT_LAST , and the WAR classloading mode is also set to PARENT_LAST . The WAR's /WEB-INF/lib has the Mojarra JSF 2 RI, and the Unified EL 2.1 jars. Despite all this, when the application starts, it tries to load some MyFaces stuff, from the inbuilt MyFaces 1.2. The class loader viewer for the WAR class loader clearly shows "org.apache.myfaces.webapp.StartupServletContextListener" getting loaded at

问题 How do I upgrade Mojarra in JBoss server and tell it use the given Mojarra 2.x JARs instead of JBoss own jboss-jsf-api_2.1_spec-2.0.1.Final.jar as indicated in startup log? If that's relevant, I am currently using JBoss AS 7.1. 回答1: The below procedure applies to JBoss AS 7.2+ , JBoss EAP 6.1+ , and JBoss WildFly 8+ and assumes that you've full control over the server installation and configuration. This upgrades the server-wide default JSF version: Download the individual Mojarra API and

问题 How do I upgrade Mojarra in JBoss server and tell it use the given Mojarra 2.x JARs instead of JBoss own jboss-jsf-api_2.1_spec-2.0.1.Final.jar as indicated in startup log? If that's relevant, I am currently using JBoss AS 7.1. 回答1: The below procedure applies to JBoss AS 7.2+ , JBoss EAP 6.1+ , and JBoss WildFly 8+ and assumes that you've full control over the server installation and configuration. This upgrades the server-wide default JSF version: Download the individual Mojarra API and

问题 I've been developing a JSF2.0 (I'm not really sure about the JSF version) application on TomEE 1.7.3 (JavaEE6 based). In my Maven pom.xml, I had too many dependencies which I've copied from many examples, but I reduced them to minimum requirements. Bellow is the "dependencies" part of my pom.xml: <dependencies> <!-- JavaEE6 --> <dependency> <groupId>javax</groupId> <artifactId>javaee-api</artifactId> <version>6.0</version> </dependency> <!-- /JavaEE6 --> <!-- OmniFaces for JSF, @Eager,