What about using getRowData() and then calling your service level to refresh the object? If it has recently changed, it would be in cache, so no hits to the DB are needed... because with the solution of the hidden parameter it is also necessary to retrieve the object in every request, isn't it?
Once I heard that the use of hidden fields breaks security in the sense that you are giving everyone the possibility to know the PK of your data. What do you think about it?
Thanks.
2005/8/31, Mathias Broekelmann <[EMAIL PROTECTED]>:
getRowData() will work too. But if the data changes between the requests
it could be possible that getRowData() returns the wrong object. Using a
parameter with a commandlink which identifies the selected object would
be safer.
Regards,
Mathias
Enrique Medina schrieb:
> Just a question...
>
> Why do you need a parameter to the commandlink? Wouldn't it be
> sufficient to have the datatable in your backing bean and simply call
> getRowData()?
>
> 2005/8/31, Jesse Alexander (KBSA 21) <[EMAIL PROTECTED]
> <mailto: [EMAIL PROTECTED]>>:
>
> -----Original Message-----
> I'm a JSF total newbbie so.. I'm sorry if I'm asking something trivial.
>
> I read a lot of tutorials on page navigation and event handling... but
> I still can't figure out how to implement a simple master/detail
> pages. I make a page with dataTable reading values from a managed bean
> but I can implement the passage to the detailed page?
> -----/Original Message-----
>
> Have you checked the tutorials at: < http://www.jsftutorials.net/>?
>
> Basically you add a command-link as a child to a column and pass it some
> identifying attribute of the current row-object as a parameter.
>
> hth
> Alexander
>
> Else join us on the IRC-channel (search the mailing-list archives for
> the coordinates)...
>
>
