OAF Vs ADF

Oracle recommendations 

If you want to integrate your extensions tightly with the E-Business Suite,
you should use the OAF Release 12 technology stack, which includes the
use of JDeveloper 10g and ADF BC (or use OAF Release 11i, which uses
JDeveloper 9i).


 If you are building a separate application that does not integrate tightly
with the E-Business Suite, but needs E-Business Suite-specific capabilities
like Flexfields and personalization, you should use the OAF Release 12
technology stack. If your application does not need to integrate with the
E-Business Suite, or doesn’t require any of the E-Business Suite-specific
capabilities enumerated above, you should use ADF 10g with SOA based
integration with E-Business Suite.


 If you are building a separate application that does not need to integrate at
all with the E-Business Suite, and you need an AJAX-style rich client user
interface, you should use ADF 11g.

ADF :

1. J2EE enabled Frame work
2. ADF Uses JSF
3. Design time page Editor
4. Minimal Java Coding
5. Declarative controller
6. Rapid Development
7. Support MVC Architecture
8. Deployed in Web logic server
9. ADF is open source
10. Support web service and SOA Service

OAF:

1. Oracle application Frame Work
2. OAF uses UIX
3. No UI page Editor
4. Complex Java coding
5. Support MVC Architecture
6. Deployed in Oracle  Application Server
7. Development is more complex