Characteristics of Page Fragments
As you build Web pages for an application, some pages may quickly become large and unmanageable. One possible way to simplify the process of building and maintaining complex pages is to use page fragments.
Large, complex pages broken down into several smaller page fragments are easier to maintain. Depending on how you design a page, the page fragments created for an entire page may also be reused in other pages. For example, suppose different parts of several pages use the same components, then you might find it beneficial to create page fragments containing those components, and reuse those page fragments in several pages or in several places on the same page. Deciding on how many page fragments to create for one or more complex pages depends on your application, the degree to which you want to reuse portions of a page between multiple pages, and the need to simplify complex pages.
Page fragments are created and used much like pages, except that page fragments are not defined as a full Web page. This enables page fragments to be used as a smaller part of a larger page. To utilize the capability of page fragments to be used as part of a page, it is likely that most pages for Fusion applications will be built as page fragments.
A page fragment does not contain f:view or af:document; its contents are simply enclosed within jsp:root. You cannot run page fragments like you can run complete JSF pages.