Adam Winer schrieb:
On 3/28/06, Werner Punz <[EMAIL PROTECTED]> wrote:
Craig, the Shale Tiger extensions are a good startin point, I read the
docs, and liked what I saw. (I also highly recommend Seam which drives
annotations to the extreme)
Anyway, having had to hack components again for an extende period of
time I still hate the huge mess the whole component API is in (no
offence to the Sun guys they did their best given that they had to
enforce 1.3+ JDKs)
A gentle reminder: JSF was not designed by "the Sun guys";
there's an expert group too. ;)
Sorry, for the mistake, I know about its origins and who is in the
expert group ;-)
Which means a total cut down of the code of at least 30% average and a
total cutdown of artefacts from 5 to 2.
Is the code reduction you're noting there from eliminating the JSP tag code?
Mostly yes, the tld definitions and taglib binding class is pure jsp,
there also could be a cut down on the faces-config parts
and standard behavior like save stating that way.
So it probably is 70% jsp gluecode elimination 30% jsf boilerplate code
elimination.
I have to run statistics but I constantly get the eery feeling that
every jsf component has a huge burden of jsp binding code, xml
boilerplates and some burden of jsf boilerplate code.
(Probably the jsp bindings alone accounting for almost 30% of the code)
