state-saving

JSF State Saving initially to server & on session timeout transfer to client?

孤者浪人 提交于 2019-12-30 05:00:27
问题 Are there any state saving method that would allow JSF application to intially save state data on server but after the session expire time interval , that state is transferred to client so that app is always responsive even after the session timeout on the server & memory is better managed on server? Or any way this could be implemented? But I expect that this should be a part of the JSF specification ! Edit After suggestion by BalusC, I'm highly impressed with the Stateless JSF principles &

JSF composite component - weird behavior when trying to save state

◇◆丶佛笑我妖孽 提交于 2019-12-18 07:05:25
问题 I'm using Glassfish 3.2.2 and JSF 2.1.11 I'm trying to create a composite component that will take as parameters a string and a max number of characters and then will show only the max amount of characters, but it will have a "more" link next to it, that when clicked will expand the text to the full length and will then have a "less" link next to it to take it back to the max number of characters. I'm seeing some weird behavior, so I'm wondering if I'm doing something wrong. Here is my

java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at com.sun.faces.renderkit.ServerSideStateHelper.getState

試著忘記壹切 提交于 2019-12-17 07:51:00
问题 When I use this code without <p:tab> it works as expected, <h:form> <p:wizard> <p:tab title="Test-1"> <h:form> <p:growl id="msg"/> <p:selectOneMenu value="#{studentController.departmentIDgenerate}"> <f:selectItems value="#{departmentController.departmentList}" var="deparet" itemLabel="#{deparet.departmentName}" itemValue="#{deparet.departmentId}"/> <p:ajax listener="#{studentController.addMessage}" update="msg"/> </p:selectOneMenu> </h:form> </p:tab> <p:tab title="Test-2"> </p:tab> </p:wizard

How to save state when extending UIComponentBase

 ̄綄美尐妖づ 提交于 2019-12-17 06:14:31
问题 I'm creating a composite component that will wrap a datatable to implement very simple paging. I need to save state (the current page number) between ajax requests. I tried creating fields in my FacesComponent, but I discovered they are wiped out during the JSF lifecycle: @FacesComponent(value = "bfTableComponent") public class BFTableComponent extends UIComponentBase implements NamingContainer { private int currentPageNumber; ... I can't seems to find a concise guide to doing this anywhere!

Saving and Restoring Application State on iOS 6 without Storyboards

旧城冷巷雨未停 提交于 2019-12-13 13:39:10
问题 I have done test app following this tutorial I try to do the same without using Storyboards and it isn't work. I have enabled state preservation and restoration in AppDelegate. I have assigned restorationIdentifier to all my controllers and their views. I think i have to implement some additional code in AppDelegate to restore rootviewcontroller, but i cannot find the right way to do this. -(BOOL)application:(UIApplication *)application shouldRestoreApplicationState:(NSCoder *)coder { return

java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at com.sun.faces.renderkit.ServerSideStateHelper.getState

孤人 提交于 2019-12-11 05:57:39
问题 When I use this code without <p:tab> it works as expected, <h:form> <p:wizard> <p:tab title="Test-1"> <h:form> <p:growl id="msg"/> <p:selectOneMenu value="#{studentController.departmentIDgenerate}"> <f:selectItems value="#{departmentController.departmentList}" var="deparet" itemLabel="#{deparet.departmentName}" itemValue="#{deparet.departmentId}"/> <p:ajax listener="#{studentController.addMessage}" update="msg"/> </p:selectOneMenu> </h:form> </p:tab> <p:tab title="Test-2"> </p:tab> </p:wizard

JSF Servlet Exception: No view save state when application session jumps between servers

北城余情 提交于 2019-12-08 12:30:56
问题 I have a web app running on in a CICS environment on Liberty servers. For workload management, the application session is set up to shift between 3 different servers, which occurs randomly during a given session. Implementing this, I am currently receiving the following error: Error 500: javax.servlet.ServletException: /{page_name}.xhtml - No saved view state could be found for the view identifier: /{page_name}.xhtml The error happens at random, but it appears that it only occurs when the

JQuery1.8 Datatables saving state on click of a button

谁都会走 提交于 2019-12-07 06:05:27
问题 I have a jsp with a table and two buttons "home" and "back" in it and have imported jquery.datatable.js in it. On click of "home" the page should load without any pagination or filter saved. and on click of "back" the table should have all the filter and pagination saved. I have tried setting the "bStateSave" flag true while initializing the data table. This always loads the table with the filter and pagination. Is there any way I can load the table with saved state on click of "back" button

JQuery1.8 Datatables saving state on click of a button

倖福魔咒の 提交于 2019-12-05 10:47:53
I have a jsp with a table and two buttons "home" and "back" in it and have imported jquery.datatable.js in it. On click of "home" the page should load without any pagination or filter saved. and on click of "back" the table should have all the filter and pagination saved. I have tried setting the "bStateSave" flag true while initializing the data table. This always loads the table with the filter and pagination. Is there any way I can load the table with saved state on click of "back" button and its original state on click of "home" button For DataTables 1.10: Below are API functions for

JSF State Saving initially to server & on session timeout transfer to client?

风流意气都作罢 提交于 2019-11-30 14:53:20
Are there any state saving method that would allow JSF application to intially save state data on server but after the session expire time interval , that state is transferred to client so that app is always responsive even after the session timeout on the server & memory is better managed on server? Or any way this could be implemented? But I expect that this should be a part of the JSF specification ! Edit After suggestion by BalusC, I'm highly impressed with the Stateless JSF principles & the current implementation for it . If anyone else here is also interested in stateless JSF being added