Oracle Application Framework 11.5.10 RUP3开发指南：入门与基础

需积分: 3 91 浏览量更新于2024-08-02 1 收藏 6.45MB PDF 举报

Oracle Application Framework (OAF) Developer's Guide Release 11.5.10 RUP3是一份详尽的技术文档，针对Oracle的高级应用程序开发框架进行了深入介绍。该指南发布于2005年12月2日，主要适用于客户、顾问或支持代表，特别是那些使用JDeveloper进行开发的人员，无论是在Windows还是Linux平台上。在本书的开头部分（第1章），开发者将学习如何入门OAF，包括设置开发环境。指南提供了针对Windows和Linux系统的JDeveloper使用指南，确保开发者熟悉开发工具的配置。随后，通过构建和运行简单的"Hello, World!"示例，新手可以快速理解OAF的基本工作原理。章节2深入探讨了OAF的核心概念。JSP应用基础是这部分的重点，它介绍了OAF页面的构成要素，如模型(Model)、视图(View)和控制器(Controller)，这些组件构成了OAF的Web应用架构，即WebBean架构。此外，指南还涵盖了OAF的Javadoc指南，帮助开发者查阅API文档。 OAF框架的状态管理是关键知识点，包括状态持久化模型（Passivation）以及根应用程序模块（如数据库会话和事务状态管理）、Servlet会话、Oracle Applications用户会话和PageContext等。这些内容对于保证应用的性能和一致性至关重要。在第3章，读者将学习如何构建一个基本的OAF应用程序，包括了解如何利用这些核心组件进行设计和开发。这涵盖了从创建应用模块到理解应用池的概念，确保了开发者能够实际操作并掌握OAF在企业级应用中的应用策略。这份指南为Oracle Application Framework的开发者提供了丰富的技术指导，从入门到进阶，帮助他们在开发过程中更好地理解和利用OAF的各种功能，从而提高开发效率和产品质量。

of several emerging standards. OA Framework technologies has driven several industry standards

and has adopted several others as they were published. Several Oracle technology architects are

active members on a number of standards drafting committees. OA Framework is J2EE based and

features several industry standards such as XML, HTML, Java, JSP, SQL and Web Services.

Architecture

OA Framework is based on the industry-standard J2EE MVC design pattern. Developers manipulate the

application's metadata using Oracle 9i JDeveloper OA Extension, while OA Framework uses the most efficient

manner to execute the application. The MVC architecture is a component-based design pattern with clean

interfaces between the Model, View, and Controller. The Model is where the application implements its

business logic. The View is where the application implements its user interface and the Controller is where the

application handles user interaction and directs business flow.

Figure 1: OA Framework MVC architecture.

OA Extension offers the following design time tools:

 UML tools to model and generate business logic.

 Guided user interface (and visual editors in a future release) to lay out client user interfaces.

 Code generation for Controller classes.

The OA Framework Model is implemented using Oracle Business Components for Java (BC4J). BC4J

provides optimized, ready-to-use implementations of the J2EE design patterns that developers otherwise

would have to code, debug, and test by hand. By leveraging BC4J's combination of tested code and

productivity tools inside the Oracle JDeveloper IDE, development teams can focus immediately and only, on

writing business logic and user interfaces instead of on designing, coding, and debugging handcrafted

application "plumbing" code.

The OA Framework View is implemented using UI XML (UIX). UIX uses XML to describe the components and

hierarchy that make up an application page. UIX also provides runtime capabilities to translate that metadata

into HTML output so that it can be shown on a Browser or a mobile device. The metadata used to describe the

UI is loaded into a database repository, called Meta Data Services (MDS), at deployment time and optionally at

design time as well.

User- and application-driven interactions are handled by the OA Controller, which is a pure Java class

implementation. Simple page flows (such as a 2-step transaction) are implemented directly into the Controller

object; others are implemented using Oracle Workflow. In a future release, business flows will be implemented

in a declarative manner similar to that used to define model and view objects.

Key Features

Integrated Development Environment

Oracle9i JDeveloper with OA Extension (OA Extension) is a world class J2EE-based integrated development

environment. Oracle customers and third party consultants have access to the same tools used by Oracle E-

Business Suite developers to build complementary applications as well as extend the Oracle E-Business Suite

applications. OA Extension provides features such as easy-to-use wizards, a hierarchy navigator, and a

property sheet. These features enable developers to populate the metadata for declarative application

business logic and user interfaces. JDeveloper offers a wealth of productivity tools such as the UML modeler,

code coach, integrated debugger, local testing environment and documentation generator.

With the OA Extension software comes a wealth of documentation and learning aids including a Developer's

Guide, Javadoc, Online Help, a Sample Library and a rich set of Tutorials.

Durable Personalizations and Extensions

Personalization is about declaratively tailoring the UI look-and-feel, layout or visibility of page content to suit a

business need or a user preference. Examples of personalization include:

 Tailoring the color scheme of the UI.

 Tailoring the order in which table columns are displayed.

 Tailoring a query result

Extensibility is about extending the functionality of an application beyond what can be done through

personalization. Examples of extensibility include:

 Adding new functional flows.

 Extending or overriding existing functional flows.

 Extending or overriding existing business logic.

OA Framework is designed with durable personalization and extensibility capabilities, achieved through the

declarative architecture and the underlying object oriented implementation.

Declarative UI component definitions are stored in the form of metadata in a database repository.

Personalizations are translated into offsets from the base metadata definition and stored separately. At

runtime, all applicable personalization metadata is loaded from the repository and layered over the base

metadata definition to produce the net effect. Product upgrades and patching only affect the base metadata

definition so that customer personalizations are preserved and continue to function properly.

Personalizations can be implemented at several levels by one of three authors: application developer,

application administrator and end user.

An end-user can create a personalization to be applied to specific user interface components that is only

visible in the context of that authoring user. For example, an end user may save an employee search result

sorted by manager and hide the employee's date of birth column. Once this personalized view is saved under

a given name, the user can retrieve that view again in the future by that name.

Application administrators and application developers have the flexibility to tailor the user experience at several

levels. They can author personalizations that affect all users, users of a particular locale, users of a particular

organization, users with a particular role and in the context of a particular function. Several levels can apply at

the same time with a predetermined precedence order that yields a very personalized user experience.

Using a combination of OA Extension wizards and built-in personalization screens, several user interface and

business logic extensions are made possible at a minimal cost to development with little-to-no maintenance

cost. In addition, Oracle E-Business Suite customers continue to enjoy the extensibility features offered by

Oracle Flexfields, Oracle Workflow and Business Events.

Consistent and Compelling User Interface

OA Framework offers developers a wide range of user interface components that make the building of

applications into a more assembly process, freeing developers from the repetitive composition of common user

interface constructs. Moreover, OA Framework's declarative approach to building application user interfaces

frees developers from the need to learn a vast array of changing technologies, while offering end users a

consistent application look and experience. OA Framework user interface components range from simple

widgets such as buttons and fields to compound components such as tables-in-tables and hierarchical grids.

User Interface Interactivity

OA Framework is always exploring the technology frontiers to enrich the interactivity of HTML-based user

interfaces. Along those lines, OA Framework provides several features:

1. Partial Page Rendering (PPR)

PPR is a means by which designated parts of a page, rather than the whole page, is refreshed when the

user performs certain actions. OA Framework supports PPR on actions such as: table record-set

navigation, table sorting, table column totaling, adding a row to a table, row-level and cell-level detail

disclosure, toggling the visibility of a Hide/Show component, populating a LOV, subtab navigation, Gantt

chart refreshing and descriptive Flexfields context switching. Moreover, developers can declaratively

enable PPR events on several components. For example, a developer can:

 Configure the selection of a poplist to cause related fields to render, be updatable, be required or be

disabled based on the selected value.

 Configure the value change of a text field to set related field values (for example, if you set a Supplier

value and tab to the next field, the dependent Supplier Site defaults automatically).

 Configure the selection of a master table's record to automatically query and display related rows in a

detail table.

2. Accelerator (Hot) Keys

OA Framework supports mnemonic accelerator keys for selected buttons and enables developers to

assign numeric access keys to product specific user actions.

3. Enhanced Save Model

OA Framework provides a default implementation to warn users when they are about to lose changes such

as when they click on a link that takes them outside the context of the current transaction. Developers can

override the default behavior on a component-by-component basis.

4. Smart Poplist

OA Framework supports a personalizable hybrid between a static poplist and a searchable list of values.

The poplist includes the most popular values a user uses to populate a particular attribute. The user can

personalize the values that show up in the poplist by picking new values from a list of values. Moreover,

the user can personalize the order in which values are listed in the poplist as well as remove less popular

values. This feature is also referred to as a LOV Choicelist.

5. LOV Auto Completion

Lists of values (LOVs) are used when the list of possible values is long and the user may want to conduct

a search before picking a value. In some business scenarios, especially with clerical jobs, the user uses a

small set of values or may find it faster to type a partial value. If the user enters a partial value in a field

that is associated with an LOV, OA Framework conducts a search before bringing up the LOV window. If

the search leads to a unique record, OA Framework completes the rest of value for the unique record and

saves the user from having to use the LOV window.

Object Oriented Reuse

OA Framework applications can be abstracted into a series of concentric layers, like an onion. The core layer

represents the database and the surface layer represents the application pages. In between is a number of

business logic and user interface layers. This layering allows for generic code and components to be

implemented at the inner layers to maximize their reuse across the outer layers. For example, attribute

validation is implemented at the Entity Object (a BC4J object-oriented representation of a database table in the

middle tier) level. All application pages that provide the user with the ability to populate or update the value of

the subject attribute would receive attribute validation for free through the underlying entity object. On the user-

interface side, reusable components can be saved as shared regions in the metadata services (MDS)

repository and reused across several pages. An administrator can choose to personalize the shared region

such that the personalization impacts all instances of the same region across pages or personalize the shared

region only in the context of the current page.

Oracle Portal Interoperability

OA Framework offers developers a simple approach to publishing OA Framework components (commonly

known as regions) as Oracle Portal-compatible portlets. Oracle Portal provides you with a common, integrated

starting point for accessing all your data. Since Oracle Portal lets you personalize the content and look of your

page, you can also personalize the application region that is displayed as a portlet. Any personalizations you

make to that portlet region appear only when you display that region from the same portlet.

Built-in Security

HTML-based applications offer great user and administrator convenience, but special care must be taken to

ensure that these applications are secure. Developing HTML applications that are truly unbreakable is very

difficult, historically requiring application developers to also be security experts. In fact, most application

developers are not security experts, and they should not need to be. It is the responsibility of the application

framework to ensure that HTML transactions are authorized, private, and free from tampering. OA Framework

provides built in protection against known HTML hacking strategies, leaving the application developer free to

concentrate on application functionality. Also, since UI components are defined in metadata rather than in

code, the security protection offered by OA Framework can be advanced to keep up with the state of the art,

without requiring applications to be rewritten.

Deployment Environment

剩余1003页未读，继续阅读

wangwangui6

粉丝: 0
资源: 97

Oracle Application Framework 11.5.10 RUP3开发指南：入门与基础

Oracle Application Framework Developer's Guide Release 11.5.10 Rup7.pdf

Oracle Application Framework Developer's Guide Release 11.5.10 RUP3.pdf

OAF开发笔记.pdf

OAF示例开发.pdf

OAF入门学习教程.pdf

Oracle Workflow Guide.pdf

Oracle Grants Accounting User’s Guide Release 11i

OAF客户化开发实例之FTP项目成果展示开发实例v1.0.pdf )

02 OAF客户化开发实例之Helpdesk公告用户显示开发实例v1.0.pdf

03OAF客户化开发实例之Helpdesk问题处理者管理员开发实例v1.0.pdf

最新资源