There's a good example of getting row-specific events in the
O'Reilly book JavaServer Faces (Hans Bergsten), pp. 173 - 178. The example
application throughout the book is to build an expense report application, and
it makes use of the summary-detail links you refer to.
However, I believe that, using this mechanism, there's no real way to get
around using something like <t:saveState> or having a
session-scoped bean. Just out of curiosity, what is the objection to using
<t:saveState>?
-
Brendan
-----Original Message-----
From: Rick Reumann [mailto:[EMAIL PROTECTED]
Sent: Friday, August 26, 2005 2:59 PM
To: MyFaces Discussion
Subject: Re: Dealing with links/buttons to fire off an action? confusion on how to set this up
On 8/26/05, Mike Kienenberger <[EMAIL PROTECTED]> wrote:You can also use dataTable.getRowData(), provided your model data is
consistent, and then you don't need to create or pass a parameter.
public void editRecord(ActionEvent event)
{
dataStore.editRecord (dataTable.getRowData());
}
Can you explain this a bit more? For example will it matter if another user ends up going to the same JSP and has a 'different' view of the dataTable while I'm working with it in the editRecord method above? I would think that it wouldnt' matter but just double checking.
--
Rick
