This content has been marked as final.
Show 5 replies
-
1. Re: Why parametes passed via JSF EL always null?
amiliosanchez Dec 10, 2008 10:14 PM (in response to amiliosanchez)anyone?
-
2. Re: Why parametes passed via JSF EL always null?
luxspes Dec 10, 2008 10:37 PM (in response to amiliosanchez)what control do you use for submit?
-
3. Re: Why parametes passed via JSF EL always null?
matt.drees Dec 10, 2008 11:10 PM (in response to amiliosanchez)
Amilio Sanchez wrote on Dec 10, 2008 20:47:<a4j:repeat value="#{someList}" var="someValue"> ... <h:selectBooleanCheckbox id="#{someUtil.generateAnIdForAPurpose(someValue)}" ...
Yeah, I don't think you can do that.
The id expression only gets evaluated once; there's only one HtmlSelectBooleanCheckbox component in the component tree. When the page renders, this component will be asked to render itself multiple times, but there's only one component.
So the id can't be row-dependent. -
4. Re: Why parametes passed via JSF EL always null?
chris.simons Dec 10, 2008 11:42 PM (in response to amiliosanchez)I agree; don't think it's possible. However, could you use an a4j:actionParam here on
someValue
and set it to your backing bean?For example, I did something similar here:
<rich:dataTable id="contactTypes" var="contactTypes" value="#{eventManager.getEventContactTypes()}" rendered="true" rowClasses="evenRows" sortMode="single" width="#{globals['dataTable.width.default']}" rows="#{englinkUtil.getDefaultDataTableRows(facesContext, null)}"> <!-- columns --> <a4j:commandLink value="Add User" action="#{userPicker.initPicker('eventManager.addContact')}" onclick="#{rich:component('defaultUserPickerModal')}.show()"> <a4j:actionparam name="selectedContactTypeId" value="#{contactTypes.id}" assignTo="#{eventManager.selectedContactTypeId}"/> </a4j:commandLink>
-
5. Re: Why parametes passed via JSF EL always null?
amiliosanchez Dec 11, 2008 12:12 AM (in response to amiliosanchez)Thanks for the suggestions I'll try them out and let you know.