HtmlCommandLink has some features that UICommandButton doesn't. For example, the abitlity to specify UIParameters, as you mentioned below.
As for the javascript usage of HCL, it's effectively mandated by the JSF spec since there's no other way to implement HCL behavior :) -Mike On 10/3/05, Stefan Betermieux <[EMAIL PROTECTED]> wrote: > Zitat von Mike Kienenberger <[EMAIL PROTECTED]>: > > > HtmlCommandLink requires javascript to work (it has to submit a form, > > and links don't submit forms without javascript). > > > > Is this what you're asking about? > > Kind of. I didn't realized that it needs to submit the form, because I > just saw > the UIParameter added to the UICommandLink and thought it would be sufficient > for the component. But a dataScroller without a dataModel will be very > incomplete ;-) > > In the meantime I am helping myself with commandButtons, maybe I write an > advanced renderer for the datascroller some time. > > Which leads me to the question why a commandLink is used over a commandButton. > If it is just because of the visual appearance: You can use CSS to let the > buttons look like a regular link and even add images. > > I think we pay a high toll if we sacrifice compatibility with non javascript > browsers (I know companies who block javascript at their central web-proxies). > What is the stance of the myfaces development team on this topic? > > Bye, > > Stefan > >
