Difference between revisions of "Rifidi App Upgrade Guide"
From RifidiWiki
(New page: =Coming Soon!= This page will show you how to upgrade your Rifidi 1.2 applications for use with Rifidi 1.3.) |
|||
| Line 1: | Line 1: | ||
| − | = | + | =Rifidi App Upgrade= |
| − | + | Some work will need to be done to switch your RifidiApp from 1.2 to 1.3. | |
| + | |||
| + | 1. Get the new SDK and create a new workspace with your application and the SDK. | ||
| + | 2. After setting the target platform, look for any core rifidi packages that have been altered. For instance, "org.rifidi.edge.core" has changed to "org.rifidi.edge". This must be changed in the manifest, the POJOs, and (if applicable) any spring files. Esper has also changed, from version 3.4 to version 4.2; this must also be changed in the manifest. POJOs can be switched over (after the manifest) by highlighting all the files and calling "organize imports" on them. | ||
| + | 3. Spring has been changed from version 2.5.6 to 3.0.5. You'll need to adjust any imported packages in your manifest, as well as changing the header of any spring XML files you might have. | ||
| + | 4. Other packages may have changed as well, and third party library versions may have updated. Check that everything is the correct version. | ||
| + | 5. You can export and deploy in the usual way. | ||
Revision as of 16:47, 6 January 2012
Rifidi App Upgrade
Some work will need to be done to switch your RifidiApp from 1.2 to 1.3.
1. Get the new SDK and create a new workspace with your application and the SDK. 2. After setting the target platform, look for any core rifidi packages that have been altered. For instance, "org.rifidi.edge.core" has changed to "org.rifidi.edge". This must be changed in the manifest, the POJOs, and (if applicable) any spring files. Esper has also changed, from version 3.4 to version 4.2; this must also be changed in the manifest. POJOs can be switched over (after the manifest) by highlighting all the files and calling "organize imports" on them. 3. Spring has been changed from version 2.5.6 to 3.0.5. You'll need to adjust any imported packages in your manifest, as well as changing the header of any spring XML files you might have. 4. Other packages may have changed as well, and third party library versions may have updated. Check that everything is the correct version. 5. You can export and deploy in the usual way.
