You can’t have JSTL evaluated in .js files. Only in .jsp files. (unless you remap the jsp servlet, but I wouldn’t advise to do so). The better approach is to define the variables in the .jsp including the .js, and pass these variables as arguments to an initializing function. Also make sure you don’t have … Read more
The #{component} is an implicit EL variable referring the current UIComponent in EL scope (see also implicit EL objects). You can usually only refer it in component’s HTML attribute or in template text children. E.g. in case of <h:inputText> it will reference an instance of UIInput class which has among others an isValid() method. <h:inputText … Read more
The answer is in the EL 2.2. specification document. Here’s an extract of relevance: A.1 Changes between Maintenance 1 and Maintenance Release 2 The main change in this release is the addition of method invokations with parameters in the EL, such as #{trader.buy(“JAVA”)}. Added one method in javax.el.ELResolver: Object invoke(ELContext context, Object base, Object method, … Read more
PrimeFaces doesn’t support it. Any EL expressions in oncomplete attribute are immediately evaluated during render response of that HTML document, not during oncomplete of the associated ajax call. Basically, the JavaScript code generated by oncomplete attribute contains the old value as it was during the page load. Your best bet is using RequestContext#addCallbackParam() to add … Read more
Fixed with a custom resolver: faces-config.xml: <application> <el-resolver>my.package.EmptyNullStringResolver</el-resolver> </application> EmptyNullStringResolver.java: /** * @author pg */ public class EmptyNullStringResolver extends ELResolver { @Override public Class<?> getCommonPropertyType(ELContext context, Object base) { return String.class; } @Override public Iterator<FeatureDescriptor> getFeatureDescriptors(ELContext context, Object base) { return null; } @Override public Class<?> getType(ELContext context, Object base, Object property) { return null; … Read more
You can set the system properties programmatically using System#setProperty(). System.setProperty(“org.apache.el.parser.COERCE_TO_ZERO”, “false”); However, you need to ensure that this is been set before JSF/EL ever get initialized. Best place would be a ServletContextListener. public class Config implements ServletContextListener { @Override public void contextInitialized(ServletContextEvent event) { System.setProperty(“org.apache.el.parser.COERCE_TO_ZERO”, “false”); } @Override public void contextDestroyed(ServletContextEvent event) { // NOOP … Read more
@Named gives a CDI managed bean an EL name to be used in view technologies like JSF or JSP. Note that in a CDI application you don’t need the @Named annotation to make a bean managed by CDI (thanks to @Karl for his comment). @ManagedBean makes the bean managed by JSF and you can: inject … Read more
You’re mixing scriptlets and EL and expecting that they run “in sync”. That just won’t work. The one is an oldschool way of writing JSPs and the other is a modern way of writing JSPs. You should use the one or the other, not both. Coming back to the concrete question, under the hoods, EL … Read more
No, it is not possible to use variable arguments in EL method expressions, let alone EL functions. Your best bet is to create multiple different named methods with a different amount of fixed arguments. public static boolean isValueIn2(Integer value, Integer option1, Integer option2) {} public static boolean isValueIn3(Integer value, Integer option1, Integer option2, Integer option3) … Read more
But, when I am deploying war file in Unix (CentOS) platform, where I have Tomcat 5.5, the EL expression doesn’t get executed and giving me output like: ${prod.id} ${prod.name} In other words, the EL expression doesn’t get evaluated at all and is showing as plain text? That can have one or more of the following … Read more