![]() Review, and migrate as necessary, any code in your migrated MAF application that connects to the SQLite database. Read the subsequent sections in this chapter that describe how these changes impact the migration of your MAF application to MAF 2.1.0 or later.įinally, MAF 2.1.0 delivered an updated SQLite database and JDBC driver. If you migrate an application to MAF 2.2.1 that was created in MAF 2.1.0 or previously migrated to MAF 2.1.0, MAF will have made already made the changes required by migration to JDK 8, management of Cordova plugins, and a new cacerts file. For SSL, it delivered a cacerts file that contains new CA root certificates. ![]() It also changed the way that JDeveloper registered plugins in your MAF application. MAF 2.1.0 used newer versions of Apache Cordova and Java. Use the information in this chapter if you migrate an application created in a pre-MAF 2.1.0 release to MAF 2.2.1. The MAF 2.1.0 release introduced significant changes described in this chapter. If your migrated application uses URL schemes to invoke other applications, configure the migrated application as described in Migrating MAF Applications that Use Customer URL Schemes to Invoke Other Applications. For more information, see Security Changes in Release 2.2.1 of MAF. MAF enables App Transport Security (ATS) by default for applications that you migrate to this release.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |