Migrating .view Files to JSF .xhtml Facelets Format
You can migrate individual .view file within a project into .xhtml files. This is convenient when you have added a JSF .view portlet to a JSF Facelets project and you want to migrate the portlet views individually. While it is permissible to mix both .view files and .xhtml files in a JSF Facelets application, you are advised to migrate the added .view files.
Important: | Be sure to migrate the entire application project before you migrate any individual .view files. For more information about migrating a .view project, see Migrating a JSF .view File Project
to JSF Facelets Format. Migrating .view files in a non-migrated project will result in missing libraries and runtime errors. |
To migrate .view files to JSF .xhtml Facelets format
Note: | Migration of .view files cannot be undone. |
Note: | If any of the .view files that are to be migrated have unsaved changes in an active editor, you are prompted to select those files for saving before converting them. If you do not select or save the files before conversion, the unsaved changes will not be included in the conversion. |
1. Locate the project you want to work with in the Project Explorer view or Navigator view.
2. Do one of the following:
To migrate an individual .view, right-click the .view file and click
CAF Tools > Migrate to JSF 2.x.
To migrate all .view files in the portlet, right-click the portlet folder and click
CAF Tools > Migrate to JSF 2.x.
To migrate all .view files in the application, right-click the WebContent folder and click
CAF Tools > Migrate to JSF 2.x.
3. On the Migrate .view panel, the .view files available for migration are displayed and selected. Clear the check box for any .view file you do not want to migrate, Click Finish to migrate the .view files and any managed bean declarations, or click Next to refine your migration selections.
Note: | If any of the .view files that are to be migrated have unsaved changes in an active editor, the wizard prompts you to select those files for saving before converting them. If you do not select the files for saving before conversion, the unsaved changes will not be included in the conversion. |
4. On the Migrate Managed Bean Declarations panel, the declarations available for migration to Java annotations are displayed and selected. Clear the check box for any declaration you do not want to migrate. For more information, see About Migrating Managed Bean Declarations. 5. Click Finish.