On Wed, Jan 13, 2010 at 3:19 PM, Ogrady, John <[email protected]> wrote: > As to the using something other than a component that generates an HTML > select element, the whole point of the article is that there is no combobox > component implementation for JSF, and those of us that work for a living and > have families simply don't have the time to write one ourselves, and so I've > shared this shortcut I figured out that can save developers a lot of time. > If I used the UIInput as you suggested, ExtJS would not be able to create a > proper combobox from it, and so the UISelect extended SelectOneMenu was the > only option. Yes ExtJS injects "strange" code, but I've found it to work > nicely and play well with all the JSF functionality so far, so what's the > harm?
Rather than spend 16 hours on a hack, why not spend 30 minutes writing a component? Custom components aren't part of "the framework". They're part of your code. It's a natural extension point for JSF application code. If you're using JSF, writing custom components is part of "working for a living", just like writing validators and actions is part of writing a struts application. It's kinda like complaining you have to write action methods for your UICommands. Yes, it takes a few more minutes to write a real component (or fake one up in facelets), but once you do it, it's there to be used for all time, trivially.
