Ah, OK. Then the <t:saveState> component from MyFaces would be more appropriate for the problem being discussed. We've used this in several applications, with no problems. All of our beans (except maybe two of them, that contain more static values) are request scope, but they carry their values through multiple pages of a conversation.
- Brendan -----Original Message----- From: Gary VanMatre [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 14, 2006 10:35 AM To: Struts Users Mailing List Subject: RE: [shale] datatables request scope >From: "CONNER, BRENDAN (SBCSI)" <[EMAIL PROTECTED]> > > As Gary mentioned, you can use the MyFaces component to > carry bean values from one request to another. I'm new to Shale, but I > saw something about a Dialog framework. Is that also supposed to > address this issue? The dialog manager will track state as its related to the execution of a dialog. Its focus is on defining a page process flow at a level that pages can be reused within various dialogs. You can define actions that can be invoked between view states that provide the glue code within the context of the executing process. Under the covers, it uses session scope for tracking dialog state. > > - Brendan > Gary --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
