I still think it's a value binding evaluation problem rather than anything else.
I recommend setting a breakpoint on isDisabled and stepping through
the value binding evaluation. I think you'll find that you've either
left userManager undefined or that existingUser isn't mapping to the
method you think it's mapping to.
What happens if you simply try to evaluate nameEditingEnabled
immediately after creating it?
On 10/11/05, Jeroen Verhagen <[EMAIL PROTECTED]> wrote:
> Hi Mike,
>
> On 10/11/05, Mike Kienenberger <[EMAIL PROTECTED]> wrote:
> > Does '#{userManager.existingUser}' match isExistingUser()? Or will it
> > only match getExistingUser()?
>
> It doesn't match either, same exception for boolean getExistingUser()
>
> What I probably should have mentioned before is that the HtmlInputText
> is not on a JSP page but on a View created from a class (using the
> ClassViewHandler example from Hans Bergstens JSF book) like this:
>
> HtmlInputText nameInputText =
> Util.createInputText(application.createValueBinding("#{userManager.currentUser.name}"),
> false);
> ValueBinding nameEditingEnabled =
> application.createValueBinding("#{userManager.existingUser}");
> nameInputText.setValueBinding("disabled", nameEditingEnabled);
>
> Hope this helps to get an answer...
>
> Thanks and regards,
>
> Jeroen
>
