| Author |
Message |
![[Post New]](/JForum/templates/default/images/icon_minipost_new.gif) 13/02/2007 06:11:00
|
robclark@rocketmail.com
Joined: 21/12/2006 00:00:00
Messages: 3
Offline
|
Hello,
I have an application written in JSC2 which I am converting over to ICEFaces. I have added a menu bar that the user will select for access to different data CRUD pages. In looking at the ICEFaces examples, the components showcase in particular, it uses JSF includes of all of the pages in a panelSet and then shows the different panels as navigation between the different screens. My question is, would this make sense or is it a best practice for applications with CRUD? I have been trying to get it to work this way, but the application keeps hanging up and losing the connection - which may be caused to multiple include pages trying to reference the same cachedRowSet. I don't want to create a unique cachedRowSet for each, as we would incur an unnecessary large memory burden for each session.
Does anyone have any tips or hints on how to best construct an AJAX application with JSC2 that has CRUD capabilities with multiple screens (without navigating to a new page)?
Thanks in advance!
Rob
|
|
|
 |
![[Post New]](/JForum/templates/default/images/icon_minipost_new.gif) 13/02/2007 09:34:43
|
frank.ye
Joined: 26/10/2004 00:00:00
Messages: 709
Offline
|
There are many ways to achieve CRUD. It will depend on your layout.
You could use the same table, but only update the model.
You only need one cachedRowSet in the session scope. All the other ones will using the same one.
Could you send a sample application for the following situation (a simple one to illustrate the problem):
The application keeps hanging up and losing the connection?
thanks,
|
|
|
 |
![[Post New]](/JForum/templates/default/images/icon_minipost_new.gif) 16/02/2007 11:51:38
|
robclark@rocketmail.com
Joined: 21/12/2006 00:00:00
Messages: 3
Offline
|
Thanks for the quick response. What I had not know is that when using page fragments (includes) as the content for panels in a panelStack, the init and destroy are called each time that panelStack switches to (selectedPanel) and from each panel. This illiminates my concern about cachedRowSets and other memory issues for each session.
I will be using the panelStack to switch between the different screens of the application.
Thanks,
Rob Clark
|
|
|
 |
|
|