Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

JSF Library Migration

Revision as of 16:33, 4 April 2007 by Gerry.kessler.oracle.com (Talk | contribs) (Add content)

Moving from JSF Tools version 0.5.0 to 1.0.0 requires an upgrade of the JSF Library Registry if present. In version 1.0.0, JSF Libraries get added to projects as classpath containers, and some changes were required in the EMF model of the registry. Once an instance of the registry has been upgraded, it will no longer be useable in earlier versions of the JSF tools.

In Version 1.0.0, references to JSF Libraries are handled as classpath container references. When you add a reference to a JSF Library, you are adding the set of jars contained within the libarary, as a container reference on the classpath. To control whether or not the library will be published or exported, will depend on whether or not you mark the library (classpath container) as being a J2EE Module Dependency. The JSF Library Reference property page has been removed. You will now use the Java Build Path property page to add, remove and edit references to JSF Libraries for a project.

The tool will automatically upgrade the JSF Libary Registry. However, the references cannot be upgraded from 0.5.0. The following manual steps will be required to upgrade an existing JSF Faceted Web project to use the new JSF Library reference mechanism:

  1. From the file system, remove any jars related to JSF Libraries found in the WEB-INF/lib directory
  2. De-select any jars related to JSF Libraries from the projects J2EE Module Dependencies property page
  3. Java Build Path --> Libraries Tab --> Add Libraries --> JSF Libraries --> select libraries
  4. J2EE Module Dependencies --> select the libraries to be published and exported

Back to the top