>Mario Ivankovits schrieb: >> But I admit having to write the html markup in an renderer is a pain. >> What about a html2jsf converter which takes a html input file and >> generates the out.write stuff? >> Should be possible.
That's basically what Facelets does, except it's an xml2jsf converter. Writing components is hard, so I've been pushing compositions instead, where you just write our your javascript and inline html and package it as a referenceable composition in your document. Maybe another idea is to take Facelet's API and basically push the current UIComponent on the EL/Variable stack, then have it apply the template for rendering? >Well for a quick solution I would see velocity, but the main problem is, >using vel on component level would mean a huge speed hit, while vel is >very fast it is not fast if you have to trigger the parsing stage for >every component. >But that does not relieve us of the burden of having to maintain a >taglib binding and two xml entries. > >But the main problem I have with the current approach is that for a >simple 10 lines of html and javascript I have 200 or more lines 3 >classes and two xml entries of component markup. >Sure there is finally a codegen generating some of that stuff, but still >maintaining thise code bloat is a huge burden. > >So we have easy client side componentization, why not use it? >
