-
1. Re: EL & Facelets problem - parameters not working?
christian.bauer Feb 12, 2008 11:26 PM (in response to tomjt111)Use code blocks. Click HELP for text formatting instructions. Then edit the text, the live preview updates if you stop typing for 3 seconds.
-
2. Re: EL & Facelets problem - parameters not working?
tomjt111 Feb 13, 2008 12:54 AM (in response to tomjt111)<ui:component> <c:if test="#{empty rendered}"> <c:set var="rendered" value="true" /> </c:if> <c:if test="#{empty action}"> <c:set var="action" value="default" /> </c:if> <h:commandLink rendered="#{rendered}" action="#{componentUtils.invokeAction(action)}" value="#{value}" > <ui:insert /> </h:commandLink> </ui:component>
The odd part with the different template problems I've run into is that some workarounds help, but nothing solves all of my problems or explains the root cause. For example, I've gotten things working by switching a test from using empty to != null. Having things work is great, but I'd feel better with some understanding of why.
-
3. Re: EL & Facelets problem - parameters not working?
tomjt111 Feb 13, 2008 2:37 PM (in response to tomjt111)The clouds may be clearing. The posting at http://www.ilikespam.com/blog/c:foreach-vs-ui:repeat-in-facelets sounds like the same type of issue I'm seeing. This matches up with the fact that my problems have been showing up in templates used with a loop (datatable and a4j:repeat).
-
4. Re: EL & Facelets problem - parameters not working?
mcarrizo May 2, 2008 1:11 AM (in response to tomjt111)Hi, Tom. My web app throws exceptions when I try to use utility.InvokeAction() or componentUtils.invokeAction(). The error is always the same:
Target Unreachable, identifier 'utility' resolved to null
Do you have any idea ? ( YOUR patience is appreciated )