Is there a solution so far?

Andrea.

From: [email protected]
To: [email protected]
Date: Mon, 22 Jun 2009 16:32:47 +0530
Subject: RE: t:dataScroller problem
















Andrea wrote:

>Hi
all,

>

>sorry for the previous blank mail (but
MS does dent BLANK mail if you use Linux+firefox....).

>

>I have a problem regarding
t:dataScroller and pageIndexVar state.

>I am trying to save the page index state
into a sessio back bean so that i can remember the page the user was browsing.

>

><t:dataScroller
pageIndexVar="#{SessionBackBean.pageindex}".....

>

>Anyway it does not remember any value.

>

>Is there someone that solved this
problem and can share some code?

>

>Thank you very much.

>

>Andrea.

 

pageIndexVar is set at request level for usage of child
components within the datascroller component. IMO you will not be able to do
what you wish to do.

It’s the same as “var” attribute on
t:datatable.

 

Regards,

Madhav







**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely 
for the use of the addressee(s). If you are not the intended recipient, please 
notify the sender by e-mail and delete the original message. Further, you are 
not 
to copy, disclose, or distribute this e-mail or its contents to any other 
person and 
any such actions are unlawful. This e-mail may contain viruses. Infosys has 
taken 
every reasonable precaution to minimize this risk, but is not liable for any 
damage 
you may sustain as a result of any virus in this e-mail. You should carry out 
your 
own virus checks before opening the e-mail or attachment. Infosys reserves the 
right to monitor and review the content of all messages sent to or from this 
e-mail 
address. Messages sent to or from this e-mail address may be stored on the 
Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***
_________________________________________________________________
Naviga al sicuro, usa Windows Live Messenger!
http://messenger.it/home_sicurezza.aspx

Reply via email to