i was migrating the jdeveloper 11.1.1.7.0 to 11.1.2.3.0 ...The synchronize with database option was disabled on all entities - migrated entities as well as new entities created in the project.
I found a solution which seems to work. we haven't found any drawbacks yet and the application runs just fine.
The problem with our project, was the type mapping value, which has been changed to "Java" during the migration. You can see your current value in project properties -> ADf Business Components -> Data Type Map. You cannot change this value in the project properties but you can change it manually in the Model.jpx. In this file changes the value of the attribute "_jbo.TypeMapEntries" to "OracleApps" (Java extended for oracle). I discovered that after this change, the "synchronize with database" context menu item was enabled again and the application ran without more changes. But, after the change, new entities are created with some other data type mappings (Long, Integer, Date, Timestamp) which in some cases were different than the existing ones. Thus we updated the complete entity model to use the "OracleApps" data types and now we don't have to worry about the entity data types anymore. And the synchronization with the database works perfectly.
I found a solution which seems to work. we haven't found any drawbacks yet and the application runs just fine.
The problem with our project, was the type mapping value, which has been changed to "Java" during the migration. You can see your current value in project properties -> ADf Business Components -> Data Type Map. You cannot change this value in the project properties but you can change it manually in the Model.jpx. In this file changes the value of the attribute "_jbo.TypeMapEntries" to "OracleApps" (Java extended for oracle). I discovered that after this change, the "synchronize with database" context menu item was enabled again and the application ran without more changes. But, after the change, new entities are created with some other data type mappings (Long, Integer, Date, Timestamp) which in some cases were different than the existing ones. Thus we updated the complete entity model to use the "OracleApps" data types and now we don't have to worry about the entity data types anymore. And the synchronization with the database works perfectly.
