Alternatively, you can use t:saveState to persist your backing bean
(teamsManager) rather than the data model (teamsManager.scheduleList).
It works the same way (saves your bean state into the component
tree), but allows you more control.
On 9/6/05, Ken [EMAIL PROTECTED] wrote:
Use
Map paramMap =
FacesContext.getCurrentInstance().getExternalContext().getRequestParameterMap();
String mode = (String)paramMap.get(PARAMETER_NAME);
However, the standard JSF way to get the current dataTable row data is
using dataTable.getRowData(), so you don't need parameters.
Hi,
Does anybody know if the following is valid :
h:form
h:dataTable value=#{teamsManager.scheduleList} var=mySchedule rows=0
width=100%
h:column
h:commandLink action=TeamHome
actionListener=#{teamsManager.teamHomeEvent}
h:outputText value=#{mySchedule.opponent}
Use tomahawks dataTable with preserveDataModel=true.
Sun's RI requires backing bean in dataModel to be in session scope; an
unnecessary cost in many cases. MyFaces will store your backing
bean in this page only; an awsome extention without cost of making
baking bean session scope!
On 9/6/05, Lou
Itis ok for a small set of data. But for large collection of data from database, it may not be a good solution. when setting preserveDataModel="true", it does not work in my case without any error message. After setting it to false, everything works as expected. Ken [EMAIL PROTECTED] wrote:
Use
5 matches
Mail list logo
