Hi. >What is being an HtmlOutputLink subclass providing you? Or for that >matter, what does HtmlCommandLink provide? Does it maybe make more >sense to provide this as a single UICommand subclass with alternate >renderers? Again, I'm completely ignorant about this component, so >there's probably more to it than that.
HtmlOutputLink will render the URI directly in the 'href' attribute; <a href="/mydir/myfile.jsf">My File</a> where HtmlCommandLink will not render the URI but use linkdummyform for navigation; <a href="#" ....>My File</a> The 'problem' is that web-crawlers can't use linkdummyform and therefore the links on the site won't be picked up. HtmlCommandLink provides a lot more dynamic functonality than HtmlOutputLink, but when site indexing is more important then you have to use HtmlOutputLink. Also site with 'static' pages doesn't need to use HtmlCommandLink for navigation -- a static reference to the page plus optional parameters are enough. I havn't look into the UICommand idea -- I just took a copy of custom.navigation and started hacking ;) Best regards, Jesper P.S. Please, Cc: me since I'm not on the list
