> You mentioned the action method in your previous email, I presume you
> were refering to the DialogNavigationHandler's action method? That
> would potentially tie behavior specific to this dialog (clearing some
> backing bean) to the generic dialog processing, which would make that
> approach far less desirable.
I was referring to the method binding expression in your transition
that would return the navigation outcome.
On my dialogs I usually have a NEXT button that I reuse via Tiles. It
has an action attribute of "#{someBackingBean.next}". This gives the
specific dialog a chance to do some final cleanup before transitioning
to the next dialog step. One example would be to check the user's
submitted value and see if there is already a similar value in the
database. If there is, the navigation outcome would point to a "Are
you Sure?" type screen?
So I was thinking that you could also dump the ref to the session bean
at this point. But then I changed my mind. It seems like
#{dialog.data} is a more logical place. That is what it was designed
for after all. As you say, if you go back to the screen it will be
more efficient then recreating the bean all over again.
> -Rahul
sean
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
