Why does the JSF action tag handler in JSP invoke rendering immediately after creation?

Posted by Pentius on Stack Overflow See other posts from Stack Overflow or by Pentius
Published on 2010-05-19T09:40:24Z Indexed on 2010/05/19 9:50 UTC
Read the original article Hit count: 228

Filed under:
|
|

Dear fellows,

I read the article "Improving JSF by Dumping JSP" from Hans Bergsten.

There I read the following:

The JSP container processes the page and invokes the JSF action tag handlers as they are encountered. A JSF tag handler looks for the JSF component it represents in the component tree. If it can't find the component, it creates it and adds it to the component tree. It then asks the component to render itself.

and furthermore

On the first request, the action creates its component and asks it to render itself.

I understand that the immediate rendering after the creation of the component is the problem here (The reference to the input component can't be resolved in the example). That's one point, why JSF doesn't fit with JSP.

But it reads as if the action tag handler itself would ask the component to render. Or is it JSP that triggers the rendering directly after the action tag handler created the component.

If it is the action tag handler, I don't understand, why this is the fault of JSP.
What is different here than from JSF intended?

Thanks for your help, I need this for my thesis.

© Stack Overflow or respective owner

Related posts about jsf

Related posts about jsp