Hmm, I'm not sure what you mean. Presumably ${processScope.tmpUser}
refers to an instance of a return listener that calls returnFromDialog
()? I realized after posting that I could always put the
returnFromDialog() call into a method on a managed bean that wasn't
tied to a specific view. I guess that reduces the need for a 'magic'
outcome for closing dialogs.
L.
On 23-Aug-06, at 11:48 PM, Matthias Wessendorf wrote:
inside my dialog, i have two pages (use the processScope for
storing stuff)
that is in my button from the last page
<tr:commandButton text="Finish">
<tr:returnActionListener value="#{processScope.tmpUser}"/>
</tr:commandButton>
On 8/23/06, Laurie Harper <[EMAIL PROTECTED]> wrote:
A dialog can be launched purely through navigation configuration,
as in
<tr:commandLink action="dialog:blah" useWindow="true" .../>
...
<navigation-rule>
<navigation-case>
<from-outcome>dialog:blah</from-outcome>
<to-view-id>/some/view</to-view-id>
</navigation-case>
</navigation-rule>
A dialog is initiated based on the from-outcome having the
appropriate prefix; no Java code is required. As far as I can tell,
that's not true for terminating a dialog, though; you have to call
RequestContext.returnFromDialog() from somewhere.
Is that correct? Or is there a 'magic' outcome that can be used to do
this implicitly, as in something like
<tr:commandLink action="dialog:CLOSE" .../>
If there isn't, would this be worth adding?
L.
--
Laurie Harper
Open Source advocate, Java geek: http://www.holoweb.net/laurie
Founder, Zotech Software: http://www.zotechsoftware.com/
--
Matthias Wessendorf
further stuff:
blog: http://jroller.com/page/mwessendorf
mail: mwessendorf-at-gmail-dot-com
--
Laurie Harper
Open Source advocate, Java geek: http://www.holoweb.net/laurie
Founder, Zotech Software: http://www.zotechsoftware.com/
