Hi, Günther: Yes, that's the reason!
John, I'm sorry. I did not mean to offend you. I guess, I was just upset, because you clearly missed some key points of JSF and your way to deal with it was swearing. I can't remember, but did you ever post your problem (or your need for a combobox) to the mailing list? I guess not, because you would definitely have gotten a better solution. The best solution to your problem would be to write your own component (maybe by extending UISelect). So you would be able to change the components behavior in a real component class rather then in your managed bean and via the binding attribute. I did that myself a couple of times for JSF 1.1, and it is really not that hard! Maybe you could somehow mention that in your blogpost, because I think that no one wants that a poor solution of a problem makes its way around the internet. You wouldn't want that yourself, would you? And I think that there's no such thing as the "alpha and omega framework". Every framework has its pros and cons. Again, I'm sorry. Regards, Jakob 2010/1/13 "Günther, Rene - Innflow AG" <[email protected]> > Hi Jakob, > > > If you use an UISelect component, then you have to be aware of the fact > that this component matches the submitted values against the possible > > values. So it has to be a hardcoded validation. > > I once recognized that too. Is that related to assure data consistency and > provide some security (prevent tampering of form fields)? > > Cheers > Rene > > > -----Ursprüngliche Nachricht----- > Von: [email protected] [mailto:[email protected]] Im > Auftrag von Jakob Korherr > Gesendet: Mittwoch, 13. Januar 2010 20:51 > An: MyFaces Discussion > Betreff: Re: JSF Combo Box for MyFaces 1.1 - one humble developer's > solution > > Hi John, > > I think it would be better for yourself to (try to) understand the concepts > of JSF's standard components first, before you write a blog post in which > you do nothing but swearing about JSF. > > If you use an UISelect component, then you have to be aware of the fact > that > this component matches the submitted values against the possible values. So > it has to be a hardcoded validation. > > So if you want a component, which does not check this, you should use the > an > UIInput component (like HtmlInputText). > > Furthermore if you want to implement a combo box for JSF, it would be A LOT > better to write a custom component then to use the binding attribute to > inject strage code into the component. But that's a thing you would know, > if > you'd understand JSF, which you clearly don't. No offence. > > You might want to take a look at the some online books about JSF, like > http://jsfatwork.irian.at/semistatic/introduction.html (written in > German). > > Regards, > Jakob > > > 2010/1/13 Ogrady, John <[email protected]> > > > Wrote up my solution for a JSF combo box - and yes, this is a shameless, > > egotistical plug for my blog, but the solution is sound. Click on the > link. > > You know you want to! > > > > http://mytechhell.com/blog/archives/432 > > > > Suggestions, corrections, and relevant puns greatly accepted and > sometimes > > even appreciated... > > ___________________________________________________________ > > John O'Grady > > Dragon Tamer > > > > Human beings, who are almost unique in having the ability to learn > > from the experience of others, are also remarkable for their apparent > > disinclination to do so. > > - Douglas Adams > > > > Those who do not learn from history are doomed to repeat it. > > - George Santayana > > > > Qui tacet consentit > > (Silence implies consent) > > ___________________________________________________________ > > > > > >
