>Adam Winer schrieb:
>> 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 brought up to the WebTier EG that UIComponentTag should instead be
implemented with the DynamicAttributes contract, but this I believe was dropped
in favor of toolability.
Really, these next specs, JSP more than anything, needs to look at all of this
extra configuration *crap* as optional metadata for tooling and special cases
instead of requiring it. All of JSF's component logic within JSP tags can be
boiled down to simple rules by contract/implementation. A
UIComponentDynamicTag with the DyanmicAttributes contract would've made
dropping in new UIComponents so much easier, but now with the other default
'error when we see #{..}' in place, I don't know think even automating this
logic is even feasible.
-- Jacob
>
>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)
>
