Oracle JDeveloper 10g Build Applications with ADF - Electronic Presentation.pdf

8/15/2019 Oracle JDeveloper 10g Build Applications with ADF - Electronic Presentation.pdf

1/398

Oracle JDeveloper 10 g : Build Applications with ADF

Electronic Presentation

D16975GC10Production 1.0May 2004D39416

®


2/398

Copyright © 2004, Oracle. All rights r eserved.

This documentation contains proprietary information of Oracle Corporation. It is provided under alicense agreement containing restrictions on use and disclosure and is also protected by copyrightlaw. Reverse engineering of the software is prohibited. If this documentation is delivered to a U.S.Government Agency of the Department of Defense, then it is delivered with Restricted Rights and thefollowing legend is applicable:

Restricted Rights Legend

Use, duplication or disclosure by the Government is subject to restrictions for commercial computersoftware and shall be deemed to be Restricted Rights software under Federal law, as set forth insubparagraph (c)(1)(ii) of DFARS 252.227-7013, Rights in Technical Data and Computer Software(October 1988).

This material or any portion of it may not be copied in any form or by any means without the expressprior written permission of the Education Products group of Oracle Corporation. Any other copying isa violation of copyright law and may result in civil and/or criminal penalties.

If this documentation is delivered to a U.S. Government Agency not within the Department ofDefense, then it is delivered with “Restricted Rights,” as defined in FAR 52.227-14, Rights in Data-General, including Alternate III (June 1987).

The information in this document is subject to change without notice. If you find any problems in thedocumentation, please report them in writing to Worldwide Education Services, Oracle Corporation,500Oracle Parkway, Box SB-6, Redwood Shores, CA 94065. Oracle Corporation does not warrantthat this document is error-free.

Oracle and all references to Oracle Products are trademarks or registered trademarks of OracleCorporation.

All other products or company names are used for identification purposes only, and may betrademarks of their respective owners.

Author

Gary WilliamsLynn Munsinger Patrice Daux

Technical Contributors and

Reviewers

Jeff GallusPam Gamer Duncan Mills

Publisher

Joseph Fernandez


3/398

Copyright © 2004, Oracle. All rights reserved.

Introduction


4/398

I-2 Copyright © 2004, Oracle. All rights reserved.

Objectives

After completing this course, you should be able to do

the following:• Design and implement business services by using

Oracle ADF Business Components

• Generate and test the end-to-end components as acomplete ADF application• Build Web-based views for an application, using

declarative tools in Oracle JDeveloper 10 g• Use Oracle JDeveloper 10 g to define user interface

functionality and application flow based on Struts


5/398I-3 Copyright © 2004, Oracle. All rights reserved.

Course Overview

This course teaches:

• How to build J2EE applications by using OracleJDeveloper 10 g

• How to build and implement business services by

using Oracle ADF Business Components• How to build MVC-based client applicationcomponents

• How to use Struts as the controller in an MVC-based application


6/398Copyright © 2004, Oracle. All rights reserved.

Oracle Application DevelopmentFramework


7/398Copyright © 2004, Oracle. All rights reserved.1-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-basedapplication 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



J2EE Platform

• Is a multit iered, distributed application model

• Supports component-based J2EE applications

Business tier

JSP/Servlet

Browser/ Application

BusinessServices

Web t ier Client tier EIS tier

Database Server J2EE Server Client Machine

Database



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 designscenarios: – Multitier – Web – Stand-alone client

• J2EE separates development tasks into specificskill areas.



J2EE Platform: Architecture Details

JSP/Servlet

Browser

BusinessServices

Webcontainer

Clientcontainer

EIS tier J2EE Server

Database Application

Client

APIs

Businesscontainer

Client Machine

JMS

JNDI RMI

JDBC

JTA

JavaMail

JAF



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 existingapplication 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.



What Is Framework-Based

Application 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 majori ty of common tasks with

sensible behavior • Enables easy customization of default behaviors• Uses standard, proven techniques and design

patterns



Understanding Framework-Based

Application Development

A framework provides base

functionality:• Standard behaviors• Data access methods• Transaction management

You can augment

or circumventbase functionality.

Provides “ hook points”

to standard functions

Your objects haveonly your code.

Framework

No messy codegeneration



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 implementingstandard J2EE design patterns (MVC)

• Provides a flexible and extensible environment byallowing multiple technology choices anddevelopment styles


15/398

Copyright © 2004, Oracle. All rights reserved.1-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


16/398


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 designpattern.


17/398


Model-View-Controller Architecture

MVC provides logical separation of an application.

Browser/ Application

Webtier Clienttier EIStier

Database

View

Controller Model

Businesstier

B u s i n

e s s S er v i c

e s


18/398


19/398


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 differentBusiness Service types in a common way.

View Controller

Model


20/398


The Model Layer

BusinessServices

Model

TopLink Mapping

ADF Bindings

ADF Data Control

WebServices

ADF Application

Module

JavaClasses

EJBSessionBeans

TopLinkQueries

ADFView Object

JavaClasses

EJBFinders

ADFEntityObject

EJB EntityBeans

JDBC


21/398


Components of the Model Layer

• Bindings:

– Metadata that describes how the UI components ona page use the values and actions provided by theBusiness 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


22/398


What Is the Controller?

On a Web page, everything significant

happens on submit or a link.• A Controller intercepts a request anddispatches it to the correct page.

• The source page does not have to know how tohandle an event or where to go next.

• The handling code does not need to know whatpage to display in response.

• The Controller separates the Model and the View.• The Controller manages the flow of a Web

application.


23/398


24/398


Controller: Summary

• Controllers are key to MVC separation

and to promote code and layer reuse.• Apache Struts is the de facto standard forWeb application controllers.

• Oracle JDeveloper 10 g supports Struts as acontroller.


25/398


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


26/398


27/398


View Technologies in

Oracle JDeveloper 10 g

• JavaServer Pages (JSP)

• UIX• ADF JClient

Creating databound clients is the same in JDeveloper

for any of these supported client technologies.


28/398


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.


29/398


ADF Technology Stack

WebServices

EJBSessionBeans

JavaBeans/Other

JSP JSF

Struts

Swing/ ADF JClient ADF UIX

ADFBusiness

Components

ADF Model

View

Controller

Model

BusinessServices


30/398


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


31/398


Summary

In this lesson, you should have learned how to:

• Identify the benefits of framework-basedapplication 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


32/398


33/398

2-2 Copyright © 2004, Oracle. All rights reserved.

Objectives

After completing this lesson, you should be able to dothe following:• Identify the typical process cycle for developing

an ADF application• List the main design-time features used to build

ADF applications• Use the course application to query products and

to perform a transaction


34/398


Project Technology Scopes

• ADF is a design-time and run-time framework forJ2EE applications.

• JDeveloper provides design-time tools to supportJ2EE development.

• There are numerous technology stacks availablefor J2EE application development.

• The choice is yours.


35/398


36/398


37/398


Building an Application

1. Create an application workspace.

2. Select the technology scope.3. Design the business services for the Model.4. Design the application page flow for the

Controller.5. Create pages for the View.


38/398


Application Workspaces

• An application workspace is a way of viewing thecomponents of your application.

• JDeveloper provides several ways to view yourapplication: – Application-based view – File system view – Code-organized view

• These views enable you to organize your project

the way that works best for you.


39/398


Application Workspace Templates

• JDeveloper provides application templates basedon technology choices.

• You can create your own template, or you canchoose the technology template for yourapplication: – Web Application (default)—ADF UIX, JSP, Struts,

and ADF Business Components – Web Application (JSP, Struts, and EJB)

– Java Application (default)—ADF JClient and ADFBusiness Components – Java Application—Java, Swing/JFC, and JavaBeans – Custom Application—All JDeveloper technologies


40/398


41/398


New Application Workspace

The application contains:

• A project for the model (business services)• A project for the View and the Controller


42/398

D i h B i S i f h


43/398


Design the Business Services for the

Model: ADF Business Components• Business Components also

contain View components(View objects).

• View objects expose data toclient applications.

• Select all the objects that youwant to expose to the client.

• The wizard creates the objects

that you need.


44/398


45/398

Create JSP Pages


46/398


Create JSP Pages

• Double-click the DataPage to create a viewcomponent.

• Use a .jsp file name extension to create a JSPpage.

• Use a .uix file name extension to create a UIXpage.

• This opens the JSP or UIX Visual Editor.

Using the Visual Editors


47/398


Using the Visual Editors

• The Data Control Palette shows the data modelthat you have defined.

• Select the data elements that you want to displayon the page.

• Use “ Drag and Drop As:” to select how you wantto display the data.

• Drag the element to the page.

Databinding: Example


48/398


Databinding: Example

Display Customer as an input form:

Adding HTML to Enhance the User


49/398


Adding HTML to Enhance the User

Interface Add HTML to enhance the user interface.

Results


50/398


Results

Right-click the Customers DataPage, and select run.

Summary


51/398


Summary


• Build a simple default application by usingJDeveloper • Describe and use an application workspace• Create default ADF Business Components• Create a simple page flow diagram• Create and edit JSP Pages


52/398


53/398


Getting Started with ADF BusinessComponents

Objectives


54/398


Objectives

After completing this lesson, you should be able to dothe following:• Identify the two groups of Business Components• Define the purpose and function of Business

Components• Create an Entity Object• Create a View Object• Create an Application Module• Use the Business Components Browser to test an

application

ADF Technology Stack


55/398


gy

WebServices

EJBSessionBeans

JavaBeans/Other

JSP ADF UIX

Struts

Swing/ ADF JClientJSF

ADFBusinessComponents

ADF Model

View

Controller

Model

BusinessServices


56/398

ADF Business Components


57/398


p

• Are a complete business tierdevelopment framework

• Implement J2EE design patternsand best practice solutions for: – Business logic

implementation – Scalability and

performance – Optimized database

interaction

• Support standarddeployment options: EJB,

Web tier, Web services

Benefits of ADF Business Components


58/398


p

• ADF Business Components increase productivity – Reusable components – Reentrant wizard-driven creation of objects – Simple O/R mapping

• They provide application logic infrastructure – Ready-to-use data functions – No need to hand-code standard data access

routines.

– You only code exceptions to standard behavior.

Business Components


59/398


The Business Components framework comprises twogroups of components:• Business Domain components

– Enforce business rules – Entity Objects, Entity Associations,

and Custom Object types• Data Model components

– Provide data access to

client applications – View Objects, View Links,and Application Modules


60/398


61/398

Business Components Model


62/398


Application tasksTransaction handlingOrderEntryApp

Applicationmodule

Viewobjects

Entity

objects

PriorityOrder ItemList

Customers Orders OrderItems

Client-FacingReusable

QueryComponents

Business DomainReusable

Business Logicand Persistence

Components

Building a Business Components Model


63/398


The basic steps to create a Business Componentsmodel are:1. Create a connection to a database.2. Create an application workspace.3. Create Entity objects based on database tables.4. Create View objects to support a client

application.5. Create an Application module to publish data

access methods.6. Test the Business Components.

Creating a Database Connection


64/398


A database connection provides access to databaseobject definitions and data.To create a connection:1. Select New Database Connection.2. Complete the connection details:

– Host name – Username and password – SID

3. Test the connection.

Creating ADF Business Components:


65/398


Entity Objects• Entity objects encapsulate the business model:

– Data – Rules – Persistence behavior

• You can create one entity object for each of thetables that you want to represent in yourapplication.

Creating ADF Business Components:b


66/398


Entity Objects

1. Select Business Components from Tables in theNew Objects Gallery.

2. Select a Database Connection.

Creating ADF Business Components:E i Obj


67/398


Entity Objects

Select the tables that you want to represent in yourapplication.

Creating ADF Business Components: ViewObj


68/398


Objects

• View objects expose data to client applications.• Create View objects that are specific to client

requirements by: – Selecting a specific attribute list – Creating nonpersistent attributes

– Supplying a where clause – Supplying an order-by clause

– Joining multiple entity objects

• Views may have Links that manage Master-Detailrelationships between View objects.

Creating ADF Business Components: ViewObj t


69/398


Objects

Customers Orders OrderItems Products

PriorityOrder ItemList

Customer NameOrder DateOrder Status

Item QuantityItem PriceProduct Description


70/398

Selecting the Attributes


71/398


• Select the attributes that you need from each ofthe entities.

• JDeveloper creates the View object with the SQLSelect statement.

Creating an Application Module


72/398


• The Application Module publishes View objects.• View objects must be part of the Application

Module for client applications to have access.• Edit the Application Module and add the Views.• Rename the View instances—use names that

make sense for your client application.

Testing the Business Components


73/398


• Right-click the Application Module and selectTest.

• Select the configuration and database connection.

Summary


74/398


In this lesson, you should have learned how to:• Describe the two groups of Business Components• Define the role of Business Components• Describe the role of an Application Module• Describe the use of customized Views

Practice 3-1: Overview


75/398


This practice covers the following topics:• Creating Business Components:

– Entity objects – View objects – Application Module

• Testing an Application Module• Creating a Business Components diagram


76/398


Building Business Logic

Objectives


77/398


After completing this lesson, you should be able todo the following:• Decide where to place business logic• Describe entity objects’ role in business logic

implementation

• Create entity objects• Describe the different methods of implementing

business logic in ADF Business Components

• Add business logic to an ADF BusinessComponents application

• Use the Business Components Modeler to create

and manage Business Components

Business Logic Validation


78/398


Middle tier

Web Container

Controller

EIS tier

ADF Business Services Tier

Client tier

ADFEntityObject

ADF Applicat ion

Module

ADFView

Object

Database

Validation

Business Logic

Validation

Client

Validation

M o d e l

Database

Implementing Validation in the BusinessServices Tier


79/398


Services Tier

Business logic tier:• Is used when creating or updating data• Assumes that existing data in the database is

valid• Is defined at entity object level• Uses programmatic or declarative techniques

– Declarative: Defined in wizards and editors – Programmatic: Coded in Java

• Is specified in Java or XML or both

Entity Object: Overview


80/398


Customers

IdNameStatusEmail

Entityobject

Attributes

Databasetable

Status List(Gold Silver Platinum)

Validationrule

ID

201

NAME

Steve

STATUS

Gold

Email

[email protected] 202 Mike Silver [email protected]

CUSTOMERS


81/398

Creating an Entity Object


82/398


• Select the BusinessComponents node inthe New Gallery, andthen select EntityObject.

• Right-click thepackage name in thenavigator, and selectNew Entity Object.

Entity Object Wizard


83/398


Select adatabaseobject.

Move to thenext step.

Entera name.

Files Generated for the CustomersEntity Object


84/398


• Customers.xml : Metadata – The Entity Object Wizard obtains all its information

from this file. – Is created by default (mandatory)

• CustomersImpl.java : Entity object class

– Extends the EntityImpl class – Is row level – Includes getter and setter methods for attributes

– Is created by default (optional)

Optional Files Generated for theCustomers Entity Object


85/398


• CustomersDefImpl.java : Entity definition class – Extends the EntityDefImpl class

– Contains run-time metadata describing the entityobject

– Describes all instances of the enti ty

• CustomersCollImpl.java : Entity collectionclass – Extends the EntityCache class

– Contains run-time querying the entity collection – Caches queried rows of the entity

Using the Business Components Modelerfor Entity Objects


86/398


1. Create a diagram from the New Gallery.2. Drag objects to the diagram.

– Entity objects – Database definitions

Using the Business Components Modelerfor Entity Objects


87/398


• Create entity objects by using the ComponentPalette.

• Use the Entity Object Editor for Entity Objectproperties.

Assigning an Initial Valueto an Entity Attribute


88/398


• Add code to the create() method inEntityImpl.java .

• create() runs automatically when the entity isinstantiated.

Select the CreateMethod checkbox to generatea create()method.

OptionalJava filesselection

Mapping an Attribute to aDatabase Sequence


89/398


1. Create a databasetrigger.

create or replace triggerinsert_ord_id

BEFORE INSERT ON ordersFOR EACH ROW

DECLAREnew_id number;

BEGINSELECT orders_seq.NextVal

INTO new_id from Dual;:new.order_id := new_id;

END;

2. Set the attribute typeto DBSequence .



90/398


This practice covers the following topics:• Initializing an attribute to a default value• Assigning a database sequence to an attribute

Adding Validation


91/398


Entity-levelvalidation

Attribute-levelvalidation

Declarative Validation Rules


92/398


• Use declarative validation rules to validate anentity attribute.

• Use the Entity Object Wizard to add and edit rules.• The Entity Object Wizard provides different types

of declarative rules:

– Compare with a single value – Compare with a list of valid values—either hard

coded or the results of a SQL query – Compare with the minimum value, maximum value,

or a range of values – Validate using a custom method

• Declarative validation is XML based.

ListValidator : Example


93/398


Specify a list of values for Customers.Status .

Customers.xml…

…


94/398


95/398

Domains: Example


96/398


protected void validate(){

try {// Make sure the user entered a valid URLjava.net.URL u = new java.net.URL(mData);

}

catch (java.net.MalformedURLException e){throw neworacle.jbo.domain.DomainValidationException("Invalid URL");

}

• URLDomain verifies that an attribute is a valid URL.• The validate() method is called by the domain’s

constructor.URLDomain.java

How to Create a Domain


97/398


1. Create the domain from the New Gallery.2. Add validation code to the validate() method

automatically created in URLDomain.java .

How to Use a Domain


98/398


Edit the entity object and change the type of anattribute to URLDomain .

URLDomainappears in the

list of types ..


99/398



100/398


This practice covers the following topics:• Adding a list validator to an attribute• Creating a domain• Assigning an attribute to a domain


101/398

Objectives


102/398


After completing this lesson, you should be able todo the following:

• Describe the role of view objects in the businesscomponents framework

• Create view objects

• Customize view objects by using the View ObjectWizard

• Define relationships between view objects

• Add calculated attributes to view objects• Explain the role of an application module• Create an application module

View Object in the ADF Architecture


103/398


EIS Tier Middle Tier

Web Container

Controller ADF Business Services Tier

Client Tier

M o d e l

ADFViewObject

ADFEntityObject

ADF Applicat ionModule

Database

Entity object View object

Overview


104/398


y j

Databasetable

ID

201202

NAME

Steve Mike

STATUS

Gold Silver

WEBSITE

http://www...http://www...

j

SELECT name, statusFROM customersORDER BY name

CustomerStatusCustomers

IDNameStatusWeb site

Mike Silver Steve GoldSusan Platinum

Name Status


105/398

Interaction Between Views andEntities: Retrieving Data


106/398


• The view object queries the database directly.• Data retrieved by the query is saved to the entity

object’s cache.

• Nonpersistent attributes are stored and retrievedfrom the view object's cache.

getAttr() VO

EO

getCalcAttr() VO


107/398


108/398

Creating a View ObjectUsing the View Object Wizard


109/398



110/398


111/398

SELECT Cust ID Cust FIRSTNAMEPriorityOrder View Object

Example of a View Object


112/398


Customers

IDFirstNameLastNameStatusEmail

Orders

IDOrderdateStatusCustidTrackingno

SELECT Cust.ID, Cust.FIRSTNAME,Cust.LASTNAME, Cust.STATUSOrd.ID, Ord.ORDERDATE,

Ord.STATUSFROM CUSTOMERS Cust, ORDERS Ord WHERE Cust.ID = Ord.CUSTOMER_ID AND Cust.status = 'Platinum'

ORDER BY Ord.ORDERDATE



113/398


Select entityobjects

Selectattributes

Edit thequery

This practice covers creating and editing a newview object.


114/398


115/398

Li k b d i i h di i

Traversing Links


116/398


public oracle.jbo.RowIterator getOrderItemsView()

• Links may be traversed in either direction.• ViewRowImpl.java contains a method to get the

associated row iterator.• Use the methods of RowIterator to move from

row to row and get individual attribute values.

For example, OrdersViewRowImpl contains themethod:

• This method returns the detail items for an order.


117/398

Using the Business Components Modeler for View Objects (II)

1 Create an empty view object from the Component


118/398


1. Create an empty view object from the ComponentPalette.

2. Drag entity objects to the view box.

1

2

Application Module in the ADF Architecture


119/398


Web Container

Middle Tier

Controller

EIS Tier


Client Tier

M o d e l

Database ADF

Appl icat ionModule

ADFView

Object

ADFEntityObject

Application Modules

• Represent the data model for clients


120/398


• Represent the data model for clients• Track all changes that affect the database

• Have one connection to the database• Provide remotely accessible methods• May be deployed to multiple platforms without

code changes• May contain other application modules


121/398

Using the Business Components Modeler for an Application Module (I)

• Drag an application module from the Applications


122/398


Navigator to the diagram.• Source view objects appear in the Application

Module box.

Using the Business Components Modeler for an Application Module (II)

1. Create an empty application module from the


123/398


p y ppComponent Palette.

2. Drag view objects to the Application Module box.

1

2

Summary



124/398


In this lesson, you should have learned how to:• Describe the role of view objects in the business

components framework• Create view objects• Customize view objects using the View Object

Wizard• Define relationships between view objects• Add calculated attributes to view objects

• Explain the role of an application module• Create an application module


This practice covers the following topics:


125/398


p g p• Adding a calculated attribute to a view object

• Modifying the source code to recalculate theattribute when the view row changes


126/398


Adding Custom Validation

Objectives

After completing this lesson, you should be able to do


127/398


p g ythe following:

• Add custom methods to validate business data• Use the typesafe data access methods• Use entity associations in business logic

• Traverse entity associations


128/398


129/398


130/398

Creating a MethodValidator for an Attribute

To create a custom validator, create a new method in


131/398


the EntityImpl.java file. Select the

EntityImpl.java file in the Structure pane or selectGo to Entity Object Class from the context menu.

Creating a MethodValidator for an Attribute

To create the custom validation as ah h d


132/398


MethodValidator , the method must:

• Be defined as public• Accept a single argument of the same type as the

attribute

• Return a Boolean value• Start with validate

public boolean validateEmail(String value)

{return (value.indexOf('@') != -1 );

}


133/398


134/398

Validating Entity Objects

If entity MethodValidators are too limiting, create ac stom method in the E tit I l j file:


135/398


public boolean checkOrderMode(){

if ( ("ONLINE".equals(getOrderMode())) ||

!(getCustomerEmail() == null))

{ //success

}

else {

// Error - online order must have email address

}}

custom method in the EntityImpl.java file:

Call EntityImpl Methods

You can also override other methods inEntityImpl java For example:


136/398


EntityImpl.java . For example:

• doDML() —Log changes in another entity• beforeCommit() —Validate multiple instances of

the same entity• remove() —Record a deletion in another entity


137/398

Associations

Associations define a relationship between entityobjects Associations:


138/398


objects. Associations:

• Facilitate access to data in related entity objects• May be based on database constraints• May be independent of database constraints

• Consist of a source (master) and a destination(detail) entity

Association Example

• A customer can place one or many orders.A d i l d b j t t


139/398


Source Destination Association

Customers Orders

• An order is placed by just one customer.

OrderPlacedBy


140/398

Association Types

• AssociationEntities are related but not completely dependent


141/398


– Entities are related but not completely dependent.

– Either end of the association can exist without theother. – It is usually a categorization.

• Composition – Destination entity is completely dependent on the

source entity. – The source entity owns the destination entity.

– No destination entity can be created without theowning entity existing first .


142/398

The “ one”side of the

The “ many”side of the

Creating Entity Associations


143/398


side of the

association

side of the

association


144/398

Traversing Associations:Destination to Source

getLineItem()

Order

ItemOrderedOnAssoc

LineItem

getTrackingNo()


145/398


public String getTrackingNo() {return getOrd().getTrackingNo(); }

• The destination entity’s EntityImpl.java filecontains methods to get and set the source entity.For example, LineItemImpl.java containsgetOrd() and setOrd() .

• You can add a method to LineItemImpl.java toget the tracking number of the order containing

this item:

getLineItem() ItemOrderedOnAssoc getTrackingNo()

Traversing Associations:Source to Destination

getLineItem()

Order

ItemOrderedOnAssoc

LineItem


146/398


• The source entity’s EntityImpl.java filecontains a method to get the destination entity.For example, OrdImpl.java contains the method:

• Use the methods of RowIterator to step fromrow to row and get individual attribute values.

public oracle.jbo.RowIterator getLineItem()

getLineItem() ItemOrderedOnAssoc

Summary

In this lesson, you should have learned how to:• Add business rules to ADF Business Components


147/398


Add business rules to ADF Business Components

• Validate entities, attributes, and domains• Test the validation rules


This practice covers the following topics:• Enforcing ListValidator rules


148/398


g

• Creating domain validation code• Testing the validation rules


149/398


Providing for Efficient Queries


150/398

Overview

View object

CustomerOrders


151/398


Customers

IDNameStatus

Email

Orders

IDCustomerIdOrderModeOrderTotal

select c.name,o.order_total fromcustomers c,orders o where

c.id=o.customer_id

getFullName()

Custom method

Expert Mode View Objects

Use expert mode queries to create custom viewobjects. Select expert mode in the Create View Object

f


152/398


Wizard or in the Query category of the View ObjectEditor.

• In normal mode, JDeveloper maintains mappingsbetween entity attributes and database columns.

Mapping Attributes in Expert Mode


153/398


• Editing a query in expert mode may invalidatethese mappings.For example, edit the CustomersView query:

• At run time, the value of the Status attribute doesnot match the value in the underlying table.

• Performing an update with the view gives alocking error.

SELECT ID, NAME, initcap(STATUS) AS StatusFROM CUSTOMERS


154/398

SQL-Based View Objects

• A SQL-based view object: – Is not based on any entity object


155/398


– Cannot be used for insert, update, or delete• Use SQL-based view objects for query-only

views, which do not need the functionality ofentity objects.

• SQL-based view objects provide betterperformance than entity-based view objects.

SELECT... VO

Creating a SQL-Based View Object

• Create a view object without selecting an entityobject in the View Object Wizard.


156/398


• Click the Query tab of the wizard, and enter yourquery in the field provided.

Implementing Custom Methods

To add custom methods to a view object, modify the ViewObjectRowImpl.java file:


157/398


public String getCustFullName(){

String custFullName = "";

custFullName = getCustFirstName() +" " + getCustLastName();

return custFullName;

}

Expose Methods to the Client Application

Expose the view object client row methods:• getCustFirstName() , getCustLastName()


158/398


• getCustFullName()

Creating a Test Client

To create a test client:1. Instantiate the application module.


159/398


2. Instantiate the view object.3. Find and manipulate data as required.4. Call custom methods as required.

5. Close the application module.

Instantiating an Application Module

• Instantiate the application module by using theConfiguration class.


160/398


• Use the fully qualified application name and theconfiguration name as arguments.

// App module name

String _am = "model.OEModule";// Configuration nameString _cf = "OEModuleLocal";

// Create an instance of the AppModule

ApplicationModule am =Configuration.createRootApplicationModule(_am,_cf);

Instantiate a View Object and Output Data

• Use findViewObject() to instantiate the viewobject.

• Iterate through the Rowset


161/398


• Iterate through the Rowset .• Display the data by using getAttribute() .

ViewObject vo = am.findViewObject("CustomersView");

while (vo.hasNext()) {CustomersViewRow row = (CustomersViewRow) vo.next();

System.out.println("Customer First Name is " +

row.getAttribute("CustLastName));}

Configuration.releaseRootApplicationModule(am,true);

Calling Custom Methods

1. Retrieve the View Object Row.2. Call the published methods on the view object.


162/398


System.out.println("Customer First Name: " +row_Cust.getCustFirstName());

System.out.println("Customer Last Name: " +row_Cust.getCustLastName());

System.out.println("Customer Full Name: " +row_Cust.getCustFullName());

Setting Parameters for the Where Clause

The Where clause of a view object’s query can containeither variables or parameters.


163/398


• Provides flexibility at run time• Can be JDBC stylecustomer_id = ?

• Can be Oracle stylecustomer_id = :1

At run time, you can assign values to the parameters.

Setting Parameters for the Where Clause


164/398


Parameters


165/398

Creating a View Object at Run time

//am is an ApplicationModuleString entity = "orders.LineItem";

• To create a new view object based on an entity:


166/398


String selectClause = "id, status, quantity";String fromClause = "line_item";String whereClause = "status = 'S'";

ViewObject shippedItemsVo =

am.createViewObjectFromQueryClauses(null, entity,selectClause, fromClause, whereClause, null);

ViewObject queryItemsVo =am.createViewObjectFromQueryStmt("",

"select id, status, quantity from line_item");

• To create a new view object based on a query:

• Check the command-line argument.• Create an oracle.jbo.Key object.

Finding Data by a Row Key


167/398


• Call findByKey() , which returns an array of row objects.

if (args.length==0) {system.out.println("Customer ID is required");System.exit(0);

}

Key custKey = new Key(new Object[] {args[0]});

Row[] customers = vo.findByKey(custKey,1);


168/398


This practice covers the following topics:• Creating a programmatic view object


169/398


• Creating parameterized queries• Creating custom methods for a view object• Testing custom methods and providing query

parameters by using a command-line Java client


170/398


Making the Model Secure

Objectives

After completing this lesson, you should be able to dothe following:• Define Java Authentication and Authorization


171/398


Services (JAAS)• Define security issues with respect to Web

applications• Use ADF Model Security design-time features• Use the ADF Business Components Browser to

test your security model

Goals of J2EE Security Architecture

• To decouple security logic from application logic• To maintain platform and vendor independence


172/398


• To ensure fine-grained access control toresources• To enable portable and secure Web applications

Overview of J2EE Security Architecture

Use JAAS APIs to:• Authenticate a client to access

the system

User


173/398


– Determine who the user is. – Can they prove it?

• Authorize clients to accessresources – Determine the role of the

authenticated user.

– What actions can a userperform? Read/Write Application

Authentication

Authorization


174/398

Java Authentication and AuthorizationServices

• JAAS supports the following authorization,authentication, and user community (realm)features:

i i l


175/398


– Principals – Subjects – Login module authentication

– Roles – Realms – Policies and permissions

• JDeveloper provides wizards and dialogs that helpmanage these objects.

JDeveloper, JAAS, and Securing the ADFModel

• JDeveloper provides application security by usingJAAS.

• ADF Business Components use the JAAS securityd fi i i f i i h d l


176/398


definitions to enforce security in the model.• You can set access roles on entities and

attributes.

• The ADF Business Component Browser uses thisproperty to control model security duringdevelopment and testing.

• JDeveloper deployment uses these access rolesto build deployment descriptors.


177/398

The jbo.security.enforce ApplicationProperty

1. Select the Application Module ConfigurationEditor.

2. Click the Properties tab.h


178/398


3. Set the jbo.security.enforce property.

Setting Entity Permissions


179/398


Entity Privileges

• The users role canupdate new rows.

• The administratorsrole can update any


180/398


role can update anyrows.

• The guests role can

only read any row.

Attribute Permissions

• Attributes inherit entity permissions.• Permissions can be overridden at the attribute

level.Th i i i i l f


181/398


• The most restrictive permissions apply—forexample: – If you set read-only at the entity level, you cannot

set update at the attribute level. – Update at the entity level can have read-only at the

attribute level.

Using the Business Components Browser

• Choose Test from the Application Module contextmenu.

• Choose AppModuleLocal for the testingconfiguration


182/398


configuration.

Testing Entity and Attribute Authorization


183/398


Summary

In this lesson, you should have learned how to:• Set the login configurator for ADF BC applications

• Enable JAAS authentication for ADF BCAdd d l


184/398


Enable JAAS authentication for ADF BC• Add users and roles• Add role-specific permissions to entities and

attributes• Test an ADF BC application security scheme


This practice covers the following topics:• Setting up SSO authentication

• Creating users and rolesAddi th i ti


185/398


Creating users and roles• Adding authorizations• Testing the authorizations

Controlling an Application with Struts


186/398


Controlling an Application with Struts


187/398

Middle Tier

Web Container

EIS Tier


Client Tier

The Controller


188/398


Controller ADF Business Services Tier

ADFEntityObject

ADF Applicat ion

Module

ADFView

Object M o d e l

Database

ADF Implements MVC Using the StrutsController

JSP ADF UIX

Struts

Swing/ ADF JClientJSFView

Controller


189/398


Struts

ADF Model

Controller

Model

Web

Services

EJBSessionBeans

JavaBeans/

Other

ADFBusiness

Components

Business

Services


190/398

Example: Page Flow Without a Controller


191/398


page2.jsp page1.jsp



192/398


page2.jsp page1.jsp

page1a.jsp



193/398


page2.jsp page1.jsp

page1a.jsp



194/398


page2.jsp page1.jsp

page1a.jsp

Example: Page Flow with a Controller

Controller Next Previous


195/398


page2.jsp page1.jsp

Example: Page Flow with a Controller

Controller Next Previous

N P i


196/398


page2.jsp page1.jsp

page1a.jsp

Next Previous

What Is Struts?

• Project from the Apache Software Foundationhttp://jakarta.apache.org/struts

• Open source framework for MVC Web-basedapplications


197/398


– XML-driven controller servlet

• De facto standard for JSP Model 2 development

• Partially declarative, partially coded• Often used with other view layers

– Tiles: A page layout mechanism using JSP

templates – Velocity: Page scripting language


198/398

Struts Components

• Struts Controller Servlet: Handles requests andmarshals results

• Struts configuration file: The roadmap for theservlet

d d


199/398


• Actions: Processes a request and sends an actionforward

• ActionForms: Passes information between theclient and the model

• TagLibs: Set of Struts library tags usable in JSPs

• Resource bundles: Text-based file used forinternationalization of messages

Struts Components Flow

StrutsController Servlet Action

HTTP Request


200/398


Forward ReturnResponse

Form

Action

execute()

Model

Page

validate()

Struts Components:The Controller Servlet

• Controls the overall application process• Does not appear in the Applications Navigator

pane of JDeveloper • Is referenced in the web .xml file


201/398


• Is designed to be extended• Is driven by XML

Struts Components:The Configuration file

• Is named struts-config.xml• Is used by the controller servlet• Provides the metadata that defines the

application:A i i ( b i )


202/398


– Action mappings (abstractions) – Page flow

– Data flow – Exception handling – Resources

Struts Components: Actions

• Actions process requests, via itsexecute() method, and return ActionForward objects that identify where control should be

forwarded.• Actions are adapters between HTTP requests and


203/398


Actions are adapters between HTTP requests andthe corresponding business logic .

• The possible tasks that can be specified for anaction are: – Forward to/represent a page – Encode page flow logic – Take data from the page and update the model

Struts Components: ActionForms (Form Beans)

• Represent HTML form data that the userenters

• Shuttle data between the view and the action: – Fields in the page are populated from the

ActionForm


204/398


ActionForm .

– On submit, the ActionForm is repopulated from

the page. – Populated ActionForm is passed to the handling

action for processing.

Struts Components:Tag Libraries

• Tag libraries integrate the JSP and controllercomponents

• – Directs the controller to thecorrect action on submit

• – Displays any errors thrown by


205/398


Displays any errors thrown bythe model, including validation

• – Outputs a string from theresource file (a field label, for example)

• Much overlap with “ newer” tag libraries, for

example JSTL


206/398

Internationalizing Your Application

To internationalize an application, performthese steps:• Create other bundle files.• Add the country code to the file name such as

ApplicationResources fr.properties .


207/398


pp _ p p

• Translate the message text:

logon.title=Entrez votre nom d’utilisateur• The servlet then checks the browser locale

variable at startup, and the corresponding file isloaded if found; otherwise the default file isloaded.

Struts inOracle JDeveloper 10 g

• JDeveloper supports Struts 1.1.• You can visualize the page flow from the modeler

and: – Drill down to JSP/UIX Visual Editor for pages– Drill down to Code Editor for actions


208/398


Drill down to Code Editor for actions

• You can edit in whatever way you choose:

– Visually – Through the Structure pane and Property Inspector – In the XML

Struts Configuration File

• It is written in XML.• It is the road map of the application.• It can be cumbersome to update directly.• JDeveloper provides a graphical editing tool,

free of XML syntax


209/398


free of XML syntax.

Defining the struts-config.xmlFile Content

The Structure pane and Property Inspector


210/398


p yp


Using the Struts Configuration Editor


211/398


p yp


The Struts Page Flow Diagram andComponent Palette


212/398


Creating a Page Flow Diagram

• Using the Component Palette, dragcomponents to the diagram.

• Components do not exist until you physicallycreate them (either as a Java class or a JSP).


213/398



214/398

Struts Components:Pages and Page Forwards

• Pages symbolize the user’s view.• Creating a page forward

(also called ActionForward ):

– Creates an action entry in the struts-config.xmlfileCreates a logical name associated with the page


215/398


– Creates a logical name associated with the pagename

• Creating a page – Makes a direct reference to the page name – Requires to be changed for every occurrence

of the page when renaming it• Pages need to physically exist to be used as the

target of a forward or link

Struts Components:Forwards and Links

• A link represents a flow between components• You can create a link (unnamed dotted line):

– Between pages – Between a page and an action

• You can create a forward (named line):


216/398


– Between actions

– Between an action and a page – Default name of the first forward is Success.

• More than one forward or link may exist at the

source of a component.

ADF provides two specialized action-subclassedcomponents:• DataPage

– Create for databound pages – Used extensively in default ADF business

ADF Components: DataAction andDataPage


217/398


component applications

– Combination of a DataAction and astandard Struts Page Forward

• DataAction – Create as a standalone action for executing

custom methods of the business service – Handles standard actions from databound pages

Summary

In this lesson, you should have learned the followingabout Struts applications:• The Struts controller servlet intercepts each

request.• The struts-config.xml file defines


218/398


components:

– Actions (Processes a request) – Action Forwards (Pass HTML form data) – Page Forwards and/or Pages (Symbolize the user’s

view of an action's result)

– Resource Bundles (Componentization of Labels andText)

– Navigation (Forwards and Page Links)


219/398

Building ADF View Components


220/398


Objectives

After completing this lesson, you should be able to dothe following:• Describe how a JSP works

• Describe the fundamental components of a JSP• Create a JSP


221/398


• Include components into JSP (HTML, Struts, and

JSTL tags)• Create a data-centric JSP using ADF data binding

What Is a JSP?

JavaServer Pages are aJ2EE component, which:• Is a “ View” in the ADF

MVC structure• Contains presentation

logic

8/15/2019 Oracle JDeveloper 10g Build Applications with

Oracle JDeveloper 10g Build Applications with ADF - Electronic Presentation.pdf

Documents

Transcript of Oracle JDeveloper 10g Build Applications with ADF - Electronic Presentation.pdf