Compared to Apex and ADF how does QAFE measure up in Oracle Forms Conversion? Here is our answer to that question. If you miss certain characteristics in this comparison table, or simply want to know more about how QAFE performs in Oracle Forms Conversion, please contact us for more information.
QAFE |
ADF |
APEX |
|
| AJAX / Web 2.0 |  |
 |
 6 |
| SOA-enabling | |
|
7 |
| Data Entry Applications | |
|
|
| Suited for both Java as non-Java developers | |
1 |
8 |
| Oracle Forms Conversion > 50% automated | |
2 |
|
| Code completion | |
|
|
| Scalable | |
|
9 |
| Open API’s | |
|
|
| Development learning curve < 1 day | |
|
|
| Debugging | |
3 |
|
| Open standard language | 4 |
|
|
| Support | 5 |
|
|
| HTML 5 ready | |
|
|
| Future-proof | |
|
|
| Single installation | |
|
|
| Coolness Factor | |
|
|
| Integration possibilities third party web services | |
|
|
| Connects to all traditional back-ends | |
|
|
| Low maintainability | |
|
|
| Upgrades / updates provided | |
|
|
| Cloud Apps | |
|
|
| Integration IDE (like Eclipse) | |
10 |
11 |
Notes:
1 Developers will have to learn Java
2 With JHeadstart. Not with ADF alone.
3 JDeveloper is a must.
4 Working with W3C.
5 From the architects and designers of QAFE.
6 Design based on Web1.0
7 Closed environment (only db + http server).
8 Need to know PL/SQL.
9 Requires tweaking in http and db.
10 JDeveloper.
11 Development in browser, SQL can be edited in any IDE.
