gt;>
>> 1.had to capture the rowdata from (> value="#{dialogScope.alist}" )
>> 2.then set Server Bean properties
>> 3.open hibernate session, begin transaction, use hibernate session
>> facilities to save,update, merge, delete or add data.
>> 4.return null;
work
> }
> }
> * What did you expect to happen?
> i expect to update my database
>
>
> * What actually happened?
> when the user enter the "edit mode" and make some changes, the new entries
> got saved "client Side"as long as the Dialog exist! even if the user left
> the "edit mode". the value="#{dialogScope.alist}" show the new user
> entries.so from the frontend view it look like every thinks going well.
>
>
> can You please give a example how to do this"
> generally define an action state as the first state of my dialogs that
> goes and fills in the necessary details "
> i work within one Dialog. so at the begining a action will take place and
> launch the dialog then another action will deliver the dataBase entries
> for each user, the user make some changes and logout, dialog end.
>
>
> Sam
>> sam
>
> Craig
>
>
--
View this message in context:
http://www.nabble.com/DialogContext-and-dataTable-tf3949337.html#a11209861
Sent from the Shale - User mailing list archive at Nabble.com.
On 6/19/07, samju <[EMAIL PROTECTED]> wrote:
public class Login extends AbstractViewController{
public String editDataTable(){
FacesContext context = FacesContext.getCurrentInstance();
DialogContext dcontext = DialogHelper.getDialogContext(context);
Object currentuser = ((appBackingBean)
dcontex
://www.nabble.com/DialogContext-and-dataTable-tf3949337.html#a11204284
Sent from the Shale - User mailing list archive at Nabble.com.
