Friday, August 24, 2012

Designing Modular Applications in Oracle ADF - Follow up

This blog post is a follow up to the previous one about modularity in Oracle ADF.
Sample applications provided in a blog posts are simplified focusing on one or few aspects described.  

Real world ADF applications and task flows can be more sophisticated:

It is a diagram (some-task-flow-defintion.xml opened in JDeveloper) of one ADF bounded task flow currently running in some production system  - probably the largest ADF bounded task flow ever built :) 
This example aimed to show, that it is important to focus on modularity and reusability aspects from a very beginning, because it might be to late when a system already evolved to some size and complexity.

Just for the statistics: elements and their occurrences used in this task flow:

adfc-config 1
class 180
control-flow-case 184
control-flow-rule 124
data-control-scope 1
default-activity 1
display-name 30
document 30
exception-handler 1
finalizer 1
fixed-outcome 92
from-activity-id 124
from-outcome 90
id 30
input-parameter 81
input-parameter-definition 4
isolated 1
managed-bean 7
managed-bean-class 7
managed-bean-name 7
managed-bean-scope 7
method 93
method-call 93
name 173
outcome 96
page 2
parameter 172
return-value 81
return-value-definition 4
task-flow-call 29
task-flow-definition 1
task-flow-reference 29
task-flow-return 3
template-reference 1
to-activity-id 184
to-string 1
train 1
train-stop 30
use-page-fragments 1
value 342
view 2
And XSL transformation (described here) used to count elements in some-task-flow-definition.xml:

No comments:

Post a Comment