It is perfectly OK to specify both binding and value at the same time. Value defines a reference to a backing bean data value property. Binding supplies a link to a backing bean UIComponent property. Two different things.
However, you almost never need to use binding. Its primary benefit is in cases where you want to dynamically alter the UIComponent tree, and that's something that should not be done for trivial reasons. Not only does it sacrifice simplicity and portability, it implies that the resulting view may be subject to radical changes in appearance, and that can confuse the users. Who generally have enough trouble even if the form looks the same all the time.
An IDE is no substitute for an Intelligent Developer.
roses are red, violets are blue. Some poems rhyme and some are a tiny ad:
Programmatically Create PDF Using Free Spire.PDF with Java