el

This question already has answers here : Identifying and solving javax.el.PropertyNotFoundException: Target Unreachable (13 answers) I got this error below when I was running my JSF page. javax.el.PropertyNotFoundException: Target Unreachable, 'null' returned null.. Warning: /createStaff.xhtml @33,125 value="#{staffBean.staff.firstName}": Target Unreachable, 'null' returned null javax.el.PropertyNotFoundException: /createStaff.xhtml @33,125 value="#{staffBean.staff.firstName}": Target Unreachable, 'null' returned null I don't get why I will run into the error when I use value= "#{staffBean

This question already has an answer here : How to concatenate Strings in EL expression? (1 answer) I have the following el expression: <af:outputText value="#{viewArticle.publish ? ('Publish on ' + viewArticle.publishDate + ' by ' + viewArticle.publishFirstName + ' ' + viewArticle.publishLastName) : 'Draft version'}"/> But I am getting java.lang.NumberFormatException: For input string: "Publish on " How can I join the string? Marcio Aguiar You can use the String.concat function: <af:outputText value="#{viewArticle.publish ? 'Publish on '.concat(viewArticle.publishDate).concat(' by ').concat

This question already has an answer here: Difference between JSP EL, JSF EL and Unified EL [closed] 2 answers I've read some time ago about the difference in 'Core JSF' but now I can't find that place. Nevertheless I don't remember that there was a word about cases when we should use ${expr} in jsf. So I'm just curious what is the difference (in a chestnut) and if there a case to use ${expr} in JSF application? To summarize in clear language: ${expression} does only get , while #{expression} can do both get and set . This is because the ${expression} is evaluated only once (immediate), while

On my current page I am using JSTL to check if data is available for my form. Problem I am facing is "if there is no data I am not seeing the text fields either". I can solve it using and tags but that would entail lot of if else if else kind of code all through the page. Can anyone suggest me a better cleaner solution to this problem? <c:if test="${salesData!=null}"> <c:if test="${fn:length(salesBundle.salesArea) > 0}"> <input type="text" id="sales_area" class="salesManagerStyle"> </c:if> </c:if> You can have multiple conditions in a test . <c:if test="${salesData != null && fn:length

Consider the following interface: public interface I { default String getProperty() { return "..."; } } and the implementing class which just re-uses the default implementation: public final class C implements I { // empty } Whenever an instance of C is used in JSP EL scripting context: <jsp:useBean id = "c" class = "com.example.C" scope = "request"/> ${c.property} -- I receive a PropertyNotFoundException : javax.el.PropertyNotFoundException: Property 'property' not found on type com.example.C javax.el.BeanELResolver$BeanProperties.get(BeanELResolver.java:268) javax.el.BeanELResolver

Please see this Expression Language styleClass="#{obj.validationErrorMap eq null ? ' ' : obj.validationErrorMap.contains('key')?'highlight_field':'highlight_row'}" Even if the map is null, highlight_row style is getting applied. So I changed to styleClass="#{empty obj.validationErrorMap ? ' ' : obj.validationErrorMap.contains('key')?'highlight_field':'highlight_row'}" Even then, highlight_row is getting applied. if the map is empty OR null I dont want any style to be applied. Any help? and reasons for this behaviour? Use empty (it checks both nullness and emptiness) and group the nested