Excellent - thank you. On Mon, 2008-04-14 at 11:13 -0700, Howard Lewis Ship wrote: > The T4 state: binding was based on the fact that ASO's in T4 had > explicit, developer-assigned logical names. > > In T5, ASOs are identified by their class name, not a > developer-assigned logical name. > > You can define a field as an ASO. > > If you place the @ApplicationState annotation on an additional boolean > field (and follow the naming convention) you can determine if the ASO > exists or not. > > You can define getters, or put @Property annotation on the fields, to > expose this information to the template and to other components. > > Some people define base classes for their pages that provide the > necessary fields, annotations and accessors. > > On Mon, Apr 14, 2008 at 9:42 AM, Jan Vissers <[EMAIL PROTECTED]> 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]
