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.
Difference between revisions of "JSF Library Migration"
m |
m (→Background) |
||
| Line 16: | Line 16: | ||
== Background == | == Background == | ||
| − | 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 (WTP 2.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 | + | 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 Library Registry. | + | The tool will automatically upgrade the JSF Library 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: |
Revision as of 17:17, 26 June 2007
Overview
Moving from JSF Tools version 0.5.0 (WTP 1.5) to 1.0.0 (WTP 2.0) requires an upgrade of the JSF Library Registry. The tool will automatically migrate your workspace when loaded using WTP 2.0, however some manual steps are required to migrate existing dynamic web projects.
Action
- Clean-up old library references for each JSF project:
- From the J2EE Module Dependencies project property page, de-select any jars related to JSF Libraries
- From the Java Build Path project property page, remove any jars related to JSF Libraries
- Ensure that no jars related to JSF Libraries remain in the WEB-INF/lib folder of the directory or in the .classpath file
- Create new library references for each JSF project:
- Java Build Path --> Libraries Tab --> Add Libraries --> JSF Libraries --> select libraries
- J2EE Module Dependencies --> select the libraries to be published and exported
Background
In version 1.0.0 (WTP 2.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 Library 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: