Yep I've read it - but to me it's unclear. I know I'm stupid :-)
Again this is my T4 case: + An ASO holds on to user identity + A base page declares this ASO as well as a ASO guard to circumvent eager creation + A component 'queries' the ASO guard in order to render some dynamic content. + The component itself doesn't declare a reference to the ASO, but uses 'state:' + The component itself uses 'page.' to get hold of the ASO in case it is created. I need this use case in T5 as well - but can't seem to get the pieces together. Help would be appreciated! -J. On Mon, 2008-04-14 at 19:15 +0200, Igor Drobiazko wrote: > Read here about the application state: > http://tapestry.apache.org/tapestry5/tapestry-core/guide/appstate.html > > On Mon, Apr 14, 2008 at 7:09 PM, Jan Vissers <[EMAIL PROTECTED]> > wrote: > Let me explain: > > I have an ASO defined in a Base class which is extended by a > page. This > page uses a component. This component should check whether the > ASO has > is created. In T4 my component could lookup page properties > and state: > binding properties very easily - somehow I'm unable to > reproduce this > mechnanism in T5. > > -J. > > > On Mon, 2008-04-14 at 18:42 +0200, Jan Vissers wrote: > > Is there an equivalent for state: binding in T5 and if so - > how can I > > use it. > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > > > -- > Best regards, > > Igor Drobiazko --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
