i dont think the behavior has been designed with the adding/removing
in mind. feel free to open a jira issue for it. i think a much easier
way to do this is to always add it and override isenabled()
-igor
On Mon, Jul 7, 2008 at 10:35 AM, Hoover, William <[EMAIL PROTECTED]> wrote:
> I am using a b
I am using a behavior that is dynamically added/removed from a TextField
based upon another components state (in order to avoid extra round trips
to the server):
final AjaxFormComponentUpdatingBehavior afcub = ...
final TextField textField = new TextField("some-id", new Model()){
protected
