mojarra

问题 I know there are a number of posts about converting empty string to null in JSF2. The usual prescription is to add the following to web.xml. <context-param> <description>Does not appear to work</description> <param-name>javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL</param-name> <param-value>true</param-value> </context-param> This just does not seem to work - at all. I then created a custom string converter to test if that would work. I explicitly added it as a converter to my

问题 I want to update my JSF application to use Mojarra version 2.1.8. I added these lines into the POM file of the WAR package: <dependency> <groupId>org.glassfish</groupId> <artifactId>javax.faces</artifactId> <version>2.1.8</version> </dependency> I also added the JSF repository. I package is build successfully with the Mojarra version 2.1.8. But when I open the GlassFish log I see that there is a Mojarra version 2.1.6 deployed. What am I missing? Do I need to make some configuration into the

问题 I am trying to write a renderer which would process the placeholder attribute on an <h:inputText> component. I headed to this path after reading JSF 2.0 strips out needed HTML5 attributes and it seems correct. Here\'s my custom renderer public class InputRenderer extends com.sun.faces.renderkit.html_basic.TextRenderer{ @Override public void encodeBegin(FacesContext context, UIComponent component) throws IOException { System.out.println(\"Rendering :\"+component.getClientId()); String

问题 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? 回答1: 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

问题 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