Remote Task Flow vs. WSRP Portlets
- by Frank Nimphius
Normal
0
false
false
false
EN-US
X-NONE
X-NONE
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin:0in;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;
mso-bidi-font-family:"Times New Roman";
mso-bidi-theme-font:minor-bidi;}
A remote task flow is bounded task flow that is deployed as
a stand-alone Java EE application on a remote server with its URL Invoke property set to url-invoke-allowed. The remote task flow
is accessed either from a direct browser GET request or, when called from
another ADF application, through the task flow call activity.
For more information about how to invoke remote task flows from
a task flow call activity see chapter 15.6.4
How to Call a Bounded Task Flow Using a URL of the Oracle Fusion Middleware
Fusion Developer's Guide for Oracle Application Development Framework at
http://docs.oracle.com/cd/E23943_01/web.1111/b31974/taskflows_activities.htm#CHDJDJEF
Compared to WRSP portlets, remote task flows in Oracle
JDeveloper 11g R1 and R2 have a functional limitation in that they cannot be
embedded as a region on a page but require the calling ADF application to
navigate off to another application and page. The difference between a remote
task flow call using the task flow call activity and a simple redirect to a
remote Java EE application is that the remote task flow has a state token
attached that allows to restore the state of the calling application upon task
flow return.
A use case for a remote task flow call activity is a "yellow
page lookup" scenario in which different ADF applications use an remote
task flow to lookup people, products or similar to return a selected value to
the calling application.
Note that remote
task flow calls need to be performed from a bounded or unbounded top level task
flow of the calling application. If called from a region (using the parent call
activity) in a page, the region state is not recovered upon task flow return.
ADF developers recently have identified remote task flows
as an architecture pattern to partition their ADF applications into independently
deployed Java EE applications. While this sounds like a desirable use of the
remote task flow feature, it is not possible to achieve for as long as remote
task flows don't render as an ADF region.
