Simplified J2EE view

Entity objects = business domain objects: data + validations - we would traditionally implement these using entity EJB's, hibernate objects etc. 
View Objects = Not exactly J2EE TO's - I find this an abstraction unique to ADF encapsulating the POJO and a query.
Application Module = the API interface / 'business service'. You write your logic and expose it using any convenient interface - java client, SOAP client, EJB interface etc. 

MVC (DataBindings - ADFm, the model; Pages - jsff or jspx, the view ; TaskFlows ADFc*, the controller) then resides on top of these in your ADF UI project and consumes these business services (or ones from a non ADFbc source). 

*These names are reflected in the packaging structure of Oracle's java libraries that implement these.

Anyway, that's my brief take on things, originally posted as a response here.

Here's the official patterns catalog page.
(I need to follow up on one of their definitions if purely for pedantic reasons)


Florin Marcus said…
Interesting comparison.

Not necessary related with the post, I do believe that biggest 'jump' from J2EE to ADF development from stateless to stateful development.

This provided that most of J2EE developers haven't been using a lot EJB stateful bean.
peterson said…
Your technical information related with java programming is very useful and interesting. Also share updated details about java in your website. Thanks for sharing this article.
Java training institute in chennai

Popular posts from this blog

Recursive calls in Oracle Integration Flows (Scenario: Paginated API calls for large Data Sets)

How to show/hide operators in adf:query advanced mode

WS Security - enabling passwordDigest authentication in an Oracle FMW environment