Toby,
Components are just POJOs - as far as your application code they have no
common type; no common interface for such actions. There is a common
interface but it is fitted onto component classes at runtime. If you
need to set properties/call methods, you must provide such interfaces.
chris
: Re: Changing a components property at runtime
Toby,
Components are just POJOs - as far as your application code they have no
common type; no common interface for such actions. There is a common
interface but it is fitted onto component classes at runtime. If you
need to set properties/call methods
@tapestry.apache.org
Sent: Tuesday, 13 May, 2008 7:10:16 PM
Subject: Re: Changing a components property at runtime
Toby,
Components are just POJOs - as far as your application code they have no
common type; no common interface for such actions. There is a common
interface but it is fitted onto component
: Tuesday, 13 May, 2008 7:10:16 PM
Subject: Re: Changing a components property at runtime
Toby,
Components are just POJOs - as far as your application code they
have no
common type; no common interface for such actions. There is a common
interface but it is fitted onto component classes at runtime
Is disabled a parameter for the component?
If so, then why not make the dynamic disabled a property of the
parent component or page, and bind the component parameter to the
parent property?
For example:
the component:
@Parameter
boolean disabled;
...
The page or component that
:16:53 PM
Subject: Re: Changing a components property at runtime
Is disabled a parameter for the component?
If so, then why not make the dynamic disabled a property of the
parent component or page, and bind the component parameter to the
parent property?
For example:
the component
Message
From: Chris Lewis [EMAIL PROTECTED]
To: Tapestry users users@tapestry.apache.org
Sent: Tuesday, 13 May, 2008 7:10:16 PM
Subject: Re: Changing a components property at runtime
Toby,
Components are just POJOs - as far as your application code they have no
common type; no common
