بسم الله الرحمن الرحيم

السلام عليكم ورحمة الله تعالى وبركاته

أريد معلومات عن ADF Task Flow

ولكم جزيل الشكر

تم تعديل 19 فبراير 201313 سنة بواسطة massara

بسم الله الرحمن الرحيم

وجدت معلومات جميلة عن الموضوع وسوف أعرضها لتعم الفائدة

Oracle ADF Task Flow Transaction FundamentalsOracle ADF Task Flow Transaction Fundamentals

Abstract

Task flows are an integral part of Oracle Application
Development Framework (ADF) applications built with
Oracle JDeveloper 11g. A task flow is a modular and
reusable unit of business navigation between views and
non-visual activities like routers and methods. Through
their design task flows provide opportunities such as
reuse, the ability to map to business processes, and
compose the overall application architecture.
Within the context of task flows they also support the
concept of the transaction allowing a collection of work to
be committed or undone in its entirety. This whitepaper
discusses the concepts and features round the
transaction and data control scope features provided by
task flows to allow ADF developers to choose the correct
combination of options to meet the user requirements.Abstract
twitter.com/adfArchSquare
Task flows are an integral part of Oracle Application
Development Framework (ADF) applications built with
Oracle JDeveloper 11g. A task flow is a modular and
reusable unit of business navigation between views and
non-visual activities like routers and methods. Through
their design task flows provide opportunities such as
reuse, the ability to map to business processes, and
compose the overall application architecture.
Within the context of task flows they also support the
concept of the transaction allowing a collection of work to
be committed or undone in its entirety. This whitepaper
discusses the concepts and features round the
transaction and data control scope features provided by
task flows to allow ADF developers to choose the correct
combination of options to meet the user requirements

Introduction

Oracle JDeveloper 11g introduces the powerful concept of task flows to the Application
Development Framework (ADF) that goes beyond the limited page flow facilities provided in
JavaServer Faces. Task flows enable the design of a modular set of views and flows that can be
reused and coupled with other task flows to create a larger application. Task flows allow
developers to align web applications closely to the concept of business processes rather than a
disparate set of web pages strung loosely together by URLs. Overall ADF task flows are a key
concept in defining the architecture of an ADF application.
The transaction and data control scope behavioral options available to bounded task flows
provide a sophisticated set of functionality for spawning and managing one or more transactions
during an ADF user's session as well as sharing state between disparate parts of the application.
Traditionally applications didn't require such features but with the increasing demands from users
and the improved capabilities of technology such functionality is becoming a requirement for
contemporary applications.
To explain the requirements around transactions let's discuss an example. Imagine an application
to support call center operators who are receiving orders from customers. First the operator must
take the customer's delivery address, and order one or more items at a time. Obviously any
application we deliver to support the staff must aid taking orders, orders are our business's
bottom line.
Taking orders from customers presents many challenges though. Customers give the wrong
address, add new items to existing orders, remove other items, change their mind, call center
staff don't have an easy job. It would be made even more difficult if the system we provided to
support them didn't assist with this chaotic process. If staff record an order's items and the
customer decides to change their delivery address, we don't want to undo all the work to start
again and reenter the address. The entry of the address should reside in a separate transaction
to recording the order items. It's this sort of problem the transactional capabilities of ADF task
flows are designed to solve. And the benefit is to the bottom line of the business in processing
customers’ orders efficiently.
This paper is designed to assist you in understanding the task flow transaction and data control
scope options available to you in order to build a sophisticated and contemporary application.Introduction
Oracle JDeveloper 11g introduces the powerful concept of task flows to the Application
Development Framework (ADF) that goes beyond the limited page flow facilities provided in
JavaServer Faces. Task flows enable the design of a modular set of views and flows that can be
reused and coupled with other task flows to create a larger application. Task flows allow
developers to align web applications closely to the concept of business processes rather than a
disparate set of web pages strung loosely together by URLs. Overall ADF task flows are a key
concept in defining the architecture of an ADF application.
The transaction and data control scope behavioral options available to bounded task flows
provide a sophisticated set of functionality for spawning and managing one or more transactions
during an ADF user's session as well as sharing state between disparate parts of the application.
Traditionally applications didn't require such features but with the increasing demands from users
and the improved capabilities of technology such functionality is becoming a requirement for
contemporary applications.
To explain the requirements around transactions let's discuss an example. Imagine an application
to support call center operators who are receiving orders from customers. First the operator must
take the customer's delivery address, and order one or more items at a time. Obviously any
application we deliver to support the staff must aid taking orders, orders are our business's
bottom line.
Taking orders from customers presents many challenges though. Customers give the wrong
address, add new items to existing orders, remove other items, change their mind, call center
staff don't have an easy job. It would be made even more difficult if the system we provided to
support them didn't assist with this chaotic process. If staff record an order's items and the
customer decides to change their delivery address, we don't want to undo all the work to start
again and reenter the address. The entry of the address should reside in a separate transaction
to recording the order items. It's this sort of problem the transactional capabilities of ADF task
flows are designed to solve. And the benefit is to the bottom line of the business in processing
customers’ orders efficiently.
This paper is designed to assist you in understanding the task flow transaction and data control
scope options available to you in order to build a sophisticated and contemporary application

What is an ADF Task Flow?

Traditional web page development involves a series of pages connected by <a href> tags. Trying
to discover how a user flows through such an application is difficult as it requires the inspection of
the <a href> tags in every page to know the navigation paths.
JavaServer Faces overcame this difficulty by prescribing the page and navigation rules between
them in a faces-config.xml file. This makes it much easier to define and determine the path the
user will take in our web applications, particularly important to enterprise applications where there
is the need to take users through a prescribed set of steps.
Oracle ADF 11g takes the JSF implementation one step further and introduces the concepts of
task flows. ADF task flows compared to JSF allow not only pages to be specified in the
application's flow, but also router logic, method calls, transaction support, save points and more.
An ADF unbounded task flow mimics the faces-config.xml implementation of JSF, where
essentially there is no entry or exit point to the application. With a bookmark containing a URL of
any of the pages within the unbounded task flow, the user can leap into the application and start
navigating the defined paths from there.What is an ADF Task Flow?
Traditional web page development involves a series of pages connected by <a href> tags. Trying
to discover how a user flows through such an application is difficult as it requires the inspection of
the <a href> tags in every page to know the navigation paths.
JavaServer Faces overcame this difficulty by prescribing the page and navigation rules between
them in a faces-config.xml file. This makes it much easier to define and determine the path the
user will take in our web applications, particularly important to enterprise applications where there
is the need to take users through a prescribed set of steps.
Oracle ADF 11g takes the JSF implementation one step further and introduces the concepts of
task flows. ADF task flows compared to JSF allow not only pages to be specified in the
application's flow, but also router logic, method calls, transaction support, save points and more.
An ADF unbounded task flow mimics the faces-config.xml implementation of JSF, where
essentially there is no entry or exit point to the application. With a bookmark containing a URL of
any of the pages within the unbounded task flow, the user can leap into the application and start
navigating the defined paths from there

It is however the bounded

task flow that brings true
power to the ADF
ecosphere. A bounded
task flow is analogous to a
Java method, with a
defined name, parameters,
entry and exit points. Each
bounded task flow can be
designed to provide a
discrete function. Bounded
task flows can be assembled together through task flow calls to create logically larger functions or
composite applications. Overall bounded task flows allow a concept rarely seen in web
application, that of modularization and reuse.
Readers should have a good knowledge of ADF task flows before continuing with this document.
At the conclusion of this document you will find a number of references can be found which will
assist in learning task flow features.It is however the bounded
task flow that brings true
power to the ADF
ecosphere. A bounded
task flow is analogous to a
Java method, with a
defined name, parameters,
entry and exit points. Each
bounded task flow can be
designed to provide a
discrete function. Bounded
task flows can be assembled together through task flow calls to create logically larger functions or
composite applications. Overall bounded task flows allow a concept rarely seen in web
application, that of modularization and reuse.
Readers should have a good knowledge of ADF task flows before continuing with this document.
At the conclusion of this document you will find a number of references can be found which will
assist in learning task flow features.

تم تعديل 21 فبراير 201313 سنة بواسطة massara

جزاك الله خير علي اضافة المعلومة ...
انا كنت هرد عليك ... بس الحمد لله انك اقدرت توصلها ...

ودة بقى شرح للتسك فلو بس بلدي شويتين

http://www.araboug.org/ib/index.php?showtopic=46000