boolean getDisabled() {
return this.disabled;
}
Tom
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Craig
McClanahan
Sent: Tuesday, October 31, 2006 2:45 PM
To: MyFaces Discussion
Subject: Re: Disabled with value
Have you tried using disabled=#{flowScope.delete.booleanValue}?
-Original Message-
From: Toppac [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 28, 2006 4:45 PM
To: users@myfaces.apache.org
Subject: RE: Disabled with value binding expression
I wanted to add onto this to see
PROTECTED] On
Behalf Of Craig
McClanahan
Sent: Tuesday, October 31, 2006 2:45 PM
To: MyFaces Discussion
Subject: Re: Disabled with value binding expression
On 10/31/06, Toppac [EMAIL PROTECTED] wrote:
I am using Facelets with MyFaces, which allows jstl page
scoped
@myfaces.apache.org
Subject: RE: Disabled with value binding expression
I wanted to add onto this to see if anyone could provide
further insight. I
am using a custom variable resolver to access some session
scoped variables.
I know the value is there because I can print it out
Don't know if this is relevant or not, but the standard resolver will
look first in request scope, so a value there will hide any var in
session scope.
Regards, Simon
Toppac wrote:
I wanted to add onto this to see if anyone could provide further insight. I
am using a custom variable resolver
Also I am using
c:set var=disabled value=false scope=page/
I typed the wrong thing from memory earlier
Toppac wrote:
I print out the value to the screen to make sure it is not empty. It
evaluates to true when I would expect it to and to false at other times.
But even when it is true it
I print out the value to the screen to make sure it is not empty. It
evaluates to true when I would expect it to and to false at other times. But
even when it is true it does not affect the inputText boxes. I also use jstl
tags throughout the page, so I am pretty sure the c taglib is defined.
I am trying to use the disabled attribute on some inputText boxes in my
application. However, everytime I try to use a binding like this
h:inputText disabled=#{mybackingBean.disabled} /
In both JSP and JSF, #{backingBeanThatDoesNotExist.propertyThatDoesNotExist}
will not throw an exception; it
On 10/31/06, Toppac [EMAIL PROTECTED] wrote:
Also I am usingc:set var=disabled value=false scope=page/This is not going to work. JSF expressions do not have access to page scope in a JSP page. You'll need to us something in request scope instead.
Craig I typed the wrong thing from memory
I am using Facelets with MyFaces, which allows jstl page scoped variables to
work. Correct me if I am wrong.
Also another thing I tried is writing a customer taglib function that will
parse my backing bean value and return the string true or false, depending
on whether the calling field should
On 10/31/06, Toppac [EMAIL PROTECTED] wrote:
I am using Facelets with MyFaces, which allows jstl page scoped variables towork. Correct me if I am wrong.Sounds like a question for the Facelets list ... but I sure wonder how Facelets makes this happen during the Apply Request Values through Invoke
See
http://wiki.java.net/bin/view/Projects/FaceletsFAQ
c:set, c:if are build time tags
I use Facelets as well and the following
works for me
h:inputText disabled=#{mybackingBean.disabled} /
and my backing bean method is defined as
public boolean getDisabled() {
return
() {
return this.disabled;
}
Tom
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Craig
McClanahan
Sent: Tuesday, October 31, 2006 2:45 PM
To: MyFaces Discussion
Subject: Re: Disabled with value binding expression
13 matches
Mail list logo
