EL uses the JavaBeans standard. So, the disable EL attribute should be
#{foo.bar} and EL will use the isBar():boolean method to retrieve the
value. You must not include the is portion of the method name.
Regards,
Bryan
h b wrote:
Hello,
I have the following backing bean:
//not actual code
If we are all allowed to vote:
+1
I for one only use MyFaces and I have a automatic
filter that removes all component library messages.
Unfortunately, my filter is not always perfect.
-Bryan
Kito D. Mann wrote:
-1
I like having them all together, and I think a lot of people use at least a
Hello,
You need to use a converter.
For my project, Cobia, I have built
a generic enum converter and enum
UISelectItems component/tag.
These are used like this:
h:selectOneRadio value=#{form.education}
layout=pageDirection
cobia:enumSelectItems type=org.example.EducationEnum/
Hello,
I am considering doing code generation of backing beans, JS files, CSS
files,
and I18N text properties files based on the JSF component model for a given
screen.
One hurdle I need to overcome is that this code generation phase must
occur during the development cycle (not at run-time).
Hello,
There is a well-known problem with JSF's choice of using a colon
as the NAMING_SEPARATOR character: The CSS standard does
not work well with HTML IDs that include a colon in the name.
So for example, if you try to style a specific input element...
h:form id='x'
h:inputText id='name' ...
that shouldn't be an issue at all
-Andrew
On 8/7/07, Bryan Basham [EMAIL PROTECTED] wrote:
Hello,
There is a well-known problem with JSF's choice of using a colon
as the NAMING_SEPARATOR character: The CSS standard does
not work well with HTML IDs that include a colon in the name.
So for example
Thanks for the replies, everyone.
After wrestling with facelets for several hours, I gave up.
I don't have time right now to fit yet another technology
into our already complex mix. Likewise, it is not the right
time for my project to migrate to JSF v1.2.
What I did discover is that you can
Hi all,
I am using JSPX syntax for my JSF pages. I occasionally need to use
raw HTML surrounded by f:verbatim tags. However, I am hitting
a problem with the Jasper compiler of these verbatim tags break the
start/end tags of the HTML.
Here's an example:
f:verbatim
div class=addItemTable
Andrew Robinson wrote:
Use Facelets instead of JSP. You will not need verbatim tags anymore with it
On 8/3/07, Bryan Basham [EMAIL PROTECTED] wrote:
Hi all,
I am using JSPX syntax for my JSF pages. I occasionally need to use
raw HTML surrounded by f:verbatim tags. However, I am hitting
verbatim tags]
I think your only other option would be to xml-escape all of the tags
enclosed in your verbatim tags.
On 8/3/07, Bryan Basham [EMAIL PROTECTED] wrote:
Thanks for the suggestion. I've never used facelets, so would you
be willing to sketch how this chunk of code would look using
By default the JSTL c:set tag stores the attribute in the PAGE scope.
However, JSF does not know about the PAGE scope. If you really need
to use c:set then specify: scope='REQUEST'.
-Bryan
Christian Nolte wrote:
Hi!
I have the following problem: I have to evaluate values which have been
set
The problem you are experiencing is true for any Java/Web
framework. An HTTP request parameter does not understand
what a Java null is but always uses the empty string . So
somewhere in your application (or framework) you have to
handle the conversion from to null.
When it comes to String
Hello kind sole ;-)
I have just created a converter with a tag. Nice little exercise.
My app has lots of names for Boolean values, such as
yes / no and enabled / disabled and so on. I used
to create a separate accessor method to convert from the
Boolean to a String, but I wanted something
kindsol wrote:
Bryan,
Can you send me what you are using for your .tld, taglib.xml, and
faces-config.xml entries for this custom converter tag? I think those
are the only three files required to register a custom tag -- no?
Thanks :)
-Sol
Here is the entry for the TLD file:
Hello.
I'm not sure what you are trying to do, but it is very easy to
use JavaScript (JS) to insert a value into a JSF component, such
as a text field. I do this all of the time. I have raw HTML/JS
client-side components and as the form is being submitted I have
JS functions that package the
Hello Mario,
In principle, you are doing the right thing by declaring the
component-class for an existing component type in the faces-config
file. So, I cannot tell from your message what is going wrong.
Can you send us the error message?
Also, be warned that it is not trivial to use a custom
Hello Balaji,
Yes, I do this all the time. Remember in XHTML you have access to the
complete DOM of the screen including form fields created by JSF components
(which render as HTML form components, ultimately).
Suppose that you have a form that has a drop-down list that (when selected)
adds
.
Regards
Balaji
-Original Message-
*From:* Bryan Basham [mailto:[EMAIL PROTECTED]
*Sent:* Friday, May 25, 2007 12:33 PM
*To:* MyFaces Discussion
*Subject:* Re: Javascript and JSF
Hello Balaji,
Yes, I do this all the time. Remember in XHTML you have access to the
complete DOM
Hello Stephane,
Yes, I have dealt with the findComponent method and JSF's
name chaining scheme. I agree with you that these should
not be hardcoded, which makes it hard to use the naming
convention unless you store some essential information in
the tag/component that helps find the other
Hello,
I am trying to build a container component that encapsulates the
complete screen:
html
head
...include scripts and CSS files
/head
body
...JSF form
/body
/html
So I have a UIScreen component and a ScreenRenderer component which
creates the basic layout. OK, that's not hard.
What
Hi all,
I just joined this discussion group. I will likely have questions
from time to time, but rather than waste your time answering
questions that have already been answered I would like to be
able to search this email list. I found the following web page:
21 matches
Mail list logo
