1 / 26

Oracle Application Development Framework

Oracle Application Development Framework. Objectives. After completing this lesson, you should be able to do the following: Describe the Java 2, Enterprise Edition (J2EE) platform Describe the benefits of framework-based application development Describe the purpose and benefits of Oracle ADF

troybyrd
Télécharger la présentation

Oracle Application Development Framework

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Oracle Application Development Framework

  2. Objectives • After completing this lesson, you should be able to do the following: • Describe the Java 2, Enterprise Edition (J2EE) platform • Describe the benefits of framework-based application development • Describe the purpose and benefits of Oracle ADF • Describe the Model-View-Controller (MVC) architecture • Describe the technologies used in each of the MVC layers

  3. J2EE Platform • Is a multitiered, distributed application model • Supports component-based J2EE applications Client Machine J2EE Server Database Server Client tier Web tier Business tier EIS tier Browser/ Application JSP/ Servlet BusinessServices Database

  4. Benefits of the J2EE Platform • “Write once, run anywhere” provides simplified component development. • J2EE separates client requirements from business logic. • J2EE provides multiple development and design scenarios: • Multitier • Web • Stand-alone client • J2EE separates development tasks into specific skill areas.

  5. J2EE Platform: Architecture Details Client Machine J2EE Server EIS tier Business container Web container Browser Client container JSP/ Servlet BusinessServices Database Application Client JNDI RMI JTA JDBC JMS JavaMail JAF APIs

  6. Building J2EE Applications • Building J2EE applications can be complex. • Development time can be extensive. • Choosing and implementing appropriate design patterns can be overwhelming. • “Do it yourself” applications often repeat existing application code. • A large portion of “Do it yourself” code is dedicated to common tasks. • The more code you write, the greater is the chance of errors. • Using an existing application framework enables you to concentrate on your business needs.

  7. What Is Framework-BasedApplication Development? • A framework: • Is a productivity layer for building applications • Is a set of intelligent cooperating software components • Is designed to be specialized for your business • Handles the majority of common tasks with sensible behavior • Enables easy customization of default behaviors • Uses standard, proven techniques and design patterns

  8. Understanding Framework-Based Application Development You can augment or circumvent base functionality. Provides “hook points” to standard functions Framework Your objects have only your code. A framework provides base functionality: • Standard behaviors • Data access methods • Transaction management No messy code generation

  9. Oracle Application Development Framework • Reduces the complexity of J2EE development by providing visual and declarative development • Increases development productivity • Less coding, more reuse • Focus on the application, not the “plumbing” • Encourages J2EE best practices by implementing standard J2EE design patterns (MVC) • Provides a flexible and extensible environment by allowing multiple technology choices and development styles

  10. Visual and Declarative Development • Visual • WYSIWYG editors • UML modelers • Structure pane • Declarative • Structure pane • Property Inspector • Code view/design view synchronization • No separate generation step—always synchronized • Underlying code always accessible

  11. Design Patterns • Design patterns: • Are proven solutions to specific problems • Are a means to an end, not the end itself • Address programming tasks, not business problems • Are reusable • Provide a framework for re-creatable results • The MVC architecture is an example of a design pattern.

  12. Model-View-Controller Architecture • MVC provides logical separation of an application. Web tier Business tier EIS tier Client tier Model Controller Business Services Browser/ Application Database View

  13. MVC Structure Controller • Handles routing to the correct page • Maps UI data changes to the Model Display Submit page Data and transactions Model View • Renders the UI • Requests data from the Model • Sends “Events” to the Model • Allows the Controller to select the next View • Stores the application state • Responds to data requests • Encapsulates business logic Request data

  14. What Is the Model? • It is a wrapper and abstraction for business services: • Handles data events from the Controller • Feeds data to the View • It manages and presents data from different Business Service types in a common way. View Controller Model

  15. The Model Layer Model ADF Bindings ADF Data Control Business Services JavaClasses EJBSessionBeans WebServices ADFApplicationModule ADFView Object JDBC EJBFinders TopLinkQueries ADF Entity Object JavaClasses EJB EntityBeans TopLink Mapping

  16. Components of the Model Layer • Bindings: • Metadata that describes how the UI components on a page use the values and actions provided by the Business Service • Data controls: • Metadata that describes the data model returned by the Business Service • The metadata has the same format for all business services. ADF Bindings ADF Data Control

  17. What Is the Controller? • On a Web page, everything significant happens on submit or a link. • A Controller intercepts a request and dispatches it to the correct page. • The source page does not have to know how to handle an event or where to go next. • The handling code does not need to know what page to display in response. • The Controller separates the Model and the View. • The Controller manages the flow of a Web application.

  18. Struts in JDeveloper • JDeveloper uses Apache Struts as a Controller. • It is popular among J2EE developers. • It has been around since 2000. • It is designed to handle views based on HTTP technology.

  19. Controller: Summary • Controllers are key to MVC separation and to promote code and layer reuse. • Apache Struts is the de facto standard for Web application controllers. • Oracle JDeveloper 10g supports Struts as a controller.

  20. What Is the View? • The MVC View is the UI of the application. • It is what the end user sees and interacts with. View Controller Model

  21. View Concept • A View does not contain application code; it contains code to represent the UI and pass events to the Controller. • Views are interchangeable without rewriting controller or model logic. • A single application can have different Views that are compatible with different types of devices (HTML browser, handheld devices, and so on).

  22. View Technologies in Oracle JDeveloper 10g • JavaServer Pages (JSP) • UIX • ADF JClient • Creating databound clients is the same in JDeveloper for any of these supported client technologies.

  23. View: Summary • Views contain only display code. • Views do not contain application logic. • Views do not contain navigation logic. • Views are independent of the Controller and the Model.

  24. ADF Technology Stack JSP ADF UIX JSF Swing/ ADF JClient View Struts Controller ADF Model Model ADF BusinessComponents EJBSessionBeans WebServices JavaBeans/Other BusinessServices

  25. ADF: Summary • Productive end-to-end development • Model-View-Controller • Visual • Declarative • Standard J2EE framework • Implements J2EE best practices • Uses the latest standards • Provides architecture choices • Is built on the MVC design pattern

  26. Summary • In this lesson, you should have learned how to: • Identify the benefits of framework-based application development • Describe the Java 2, Enterprise Edition (J2EE) platform • Define the components of the Model-View-Controller architecture • Describe the benefits of Oracle Application Development Framework (ADF) • Describe the technologies used in each of the MVC layers

More Related