You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@shale.apache.org by Torsten Krah <tk...@fachschaft.imn.htwk-leipzig.de> on 2006/11/06 11:54:57 UTC
Transparent Dialog Data?
Hi again :-).
If i want to access my dialog data, i have to use
#{dialog.data.myproperty} for example.
Reading some papers of Craig, there was once plans to make this
transparent - which would be nice because i can reuse my view
definitions for dialog views and non dialog ones.
Whats the state at this front? Is there already any progress?
Torsten
Re: Transparent Dialog Data?
Posted by Torsten Krah <tk...@fachschaft.imn.htwk-leipzig.de>.
Hm might be a good idea, thx for input.
Torsten
Am Montag, den 06.11.2006, 08:22 -0800 schrieb Craig McClanahan:
> On 11/6/06, Torsten Krah <tk...@fachschaft.imn.htwk-leipzig.de> wrote:
> >
> > Hi again :-).
> >
> > If i want to access my dialog data, i have to use
> > #{dialog.data.myproperty} for example.
> > Reading some papers of Craig, there was once plans to make this
> > transparent - which would be nice because i can reuse my view
> > definitions for dialog views and non dialog ones.
> >
> > Whats the state at this front? Is there already any progress?
>
>
> How do you mean "transparent"? Are you wanting to simply use the same views
> inside a dialog and outside?
>
> Your best strategy would be to build a simple session scoped bean, stored
> under key "dialog", that has a "data" property containing your state
> information. When executed outside a dialog, the normal expression
> evaluation process will be performed, so expressions like "#{
> dialog.data.myproperty}" will still work as you expect.
>
> Torsten
> >
> >
> >
> Craig
Re: Transparent Dialog Data?
Posted by Craig McClanahan <cr...@apache.org>.
On 11/6/06, Torsten Krah <tk...@fachschaft.imn.htwk-leipzig.de> wrote:
>
> Hi again :-).
>
> If i want to access my dialog data, i have to use
> #{dialog.data.myproperty} for example.
> Reading some papers of Craig, there was once plans to make this
> transparent - which would be nice because i can reuse my view
> definitions for dialog views and non dialog ones.
>
> Whats the state at this front? Is there already any progress?
How do you mean "transparent"? Are you wanting to simply use the same views
inside a dialog and outside?
Your best strategy would be to build a simple session scoped bean, stored
under key "dialog", that has a "data" property containing your state
information. When executed outside a dialog, the normal expression
evaluation process will be performed, so expressions like "#{
dialog.data.myproperty}" will still work as you expect.
Torsten
>
>
>
Craig