Sean, I could not figure out form the documentation which data is kept
during conversation time, is it the page controller, or all data
accessed during conversation time?
Werner
Sean Schofield schrieb:
Shale dialogs do, however, have a mechanism for storing objects
between requests. So in
If memory serves me its whatever is in #{dialog.data}. I believe that
object is a Map that you can put whatever you want into it. I can't
say for sure b/c I don't have the source in front of me and its been a
while since I worked on it.
Sean
On 2/27/06, Werner Punz [EMAIL PROTECTED] wrote:
On 2/27/06, Sean Schofield [EMAIL PROTECTED] wrote:
If memory serves me its whatever is in #{dialog.data}.I believe thatobject is a Map that you can put whatever you want into it.I can'tsay for sure b/c I don't have the source in front of me and its been awhile since I worked on it.
It is correct
CONNER, BRENDAN (SBCSI) wrote:
After having done several native MyFaces application implementations,
I'm just starting to do initial research into Shale. The motivation to
do this is that, from my understanding, Shale offers a framework
allowing relatively painless debugging of JSF actions.
I
Shale dialogs do, however, have a mechanism for storing objects
between requests. So in that sense they are similar to t:saveState.
I've never really used save-state before but I have some experience
with Shale dialogs.
Shale dialogs are excellent. Its the only feature of Shale that I am
using
After having done several native MyFaces application implementations,
I'm just starting to do initial research into Shale. The motivation to
do this is that, from my understanding, Shale offers a framework
allowing relatively painless debugging of JSF actions.
I noticed on the site that Shale
6 matches
Mail list logo
