is your bean request- or session-scoped?
if you are using a session-scoped bean, you probably don't need
t:saveState at all--your data would still be there without hitting JDBC
again.
if you are using a request-scoped bean, you probably want something like
<t:saveState value="#{bean.objectId}"/> so that your backing-bean
actions can re-fetch the bean from the business/DAO layer. (Typically
you use t:saveState as a replacement for <input type="hidden">.)
you would rarely want to use t:saveState on the whole bean.
-- Bill
> 1) Why do you use <t:saveState> on the whole bean?
>
> 2) When you want you data to be fetched? If you need to refresh on any
> request, why don't you put the JDBC call directly in the getter
> method?
>
> Cosma
>
> 2006/6/22, Surapuraju, Vamsi <[EMAIL PROTECTED]>:
>>
>>
>> Hi,
>> I am initializing the page data using JDBC call in bean constructor
and I
>> am saving the whole bean state using t:saveState on the jsf page.
Since bean
>> is saved and when I hit the browser refresh on the page it is not
going to
>> database to fetch the data. Does anyone has any ideas on how to fix this
>> issue?
--
Bill Schneider
Chief Architect
Vecna Technologies
5004 Lehigh Rd.
College Park, MD 20740
[EMAIL PROTECTED]
t: 240-737-1640
f: 301-699-3180
