I
think that, in Rick's case, he was looking up data in the database, populating
his list bean, transferring control to a page that had a dataTable set up to
list the contents of the bean (which included a link in each row). When
the use clicks the link, an action is invoked which grabs detail about a
particular employee, stashes that into another bean, and then transfers control
to an edit screen. The user edits the data on the edit screen and hits
Save, at which point an action is invoked to save the data, requery the data,
repopulate the list bean, and display the list of employees
again.
Rick,
is that similar to what you're doing?
-
Brendan
-----Original Message-----Can you guys explain the dataflow based on transaction point, when do you need save in database? when just want refresh table....?
From: Zhong Li [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 01, 2005 3:06 PM
To: MyFaces Discussion
Subject: Re: more on architecture really confused on something (shocker:)
