{"id":33845,"date":"2023-02-14T15:18:01","date_gmt":"2023-02-14T09:48:01","guid":{"rendered":"https:\/\/jassweb.com\/solved\/solved-fview-and-richpage-inside-or-outside\/"},"modified":"2023-02-14T15:18:01","modified_gmt":"2023-02-14T09:48:01","slug":"solved-fview-and-richpage-inside-or-outside","status":"publish","type":"post","link":"https:\/\/jassweb.com\/solved\/solved-fview-and-richpage-inside-or-outside\/","title":{"rendered":"[Solved] f:view and rich:page: inside or outside?"},"content":{"rendered":"

[ad_1]
\n<\/p>\n

\n
\n
<\/div>\n
\n
\n

The <f:view><\/code> runs as being a taghandler during view build time, setting the specified attributes as properties of the current UIViewRoot<\/code> and\/or the HttpServletResponse<\/code> instance.<\/p>\n

So, if some taghandler (not UI component!) is encountered before<\/em> the <f:view><\/code> and relies on one of those attributes, then it will miss hit. However, <rich:page><\/code> is an UI component which runs during view render time which is long after view build time, so it will guaranteed have access to the right attribute values, even if it appears before the <f:view><\/code> in the tree.<\/p>\n

In any case, even though it’s merely a “metadata” tag (it can be placed anywhere in the view, even duplicated\/nested), most self-documenting is to just put the <f:view><\/code> as outermost tag of the tree.<\/p>\n

See also:<\/h3>\n