You will use wizards to quickly create an application and projects, and a blank ADF bounded task flow for each train. The first train you will create consists of four pages (or train stops) that guide an end user to the completion of a task. The second train you will create consists of two pages in a multistep subtask. The second train will be called from
one of the train stops in the first train sequence.
You will use wizards to quickly create an application and projects, and a blank ADF bounded task flow for each train. The first train you will create consists of four pages (or train stops) that guide an end user to the completion of a task. The second train you will create consists of two pages in a multistep subtask. The second train will be called from one of the train stops in the first train sequence.
To create a train sequence in a bounded task flow, you will use the task flow diagrammer and Component Palette to draw and connect train stops, call another train, change the train sequence, and add exit points. You will also add control flow rules to define how control flow passes from the called train back to the calling train when the called train flow exits. Next you will create a page template, add the ADF Train component, and bind the component to the train model. Then you will use the template to create JSF page fragments for the train stops. Finally, you will create a JSF page that consumes the first bounded task flow as an ADF region, then run the page.
| Purpose | Duration | Application |
|---|
This tutorial shows you how to create bounded task flows with a train sequence that represents activities in a multistep page flow. To see the complete application you will create, click the Download button to download a zip of the final application, and then unzip it in your JDevelopermywork folder. | 40 minutes |  |
From the main menu, choose File > New. In the New Gallery, expand the General category and select Applications. Then in the Items list, select Fusion Web Application (ADF) and click OK.
The JDeveloper application is the highest level in the organizational structure. While you are developing your application, it stores information about the objects you are working with.
Read more...To follow along with the example, enter TrainWebApp as the application name.
The application template you select determines the initial project structure, that is, the named project folders within the application workspace, and the application libraries that will be added.
Read more...Accept the defaults and click
Finish.
The Application Overview window opens by default in the editor window area when you create a new application. You can optionally close the window, since you will not be using it to create objects for this application.
All objects that you create within JDeveloper appear in the Application Overview file summary pages, arranged by object type. You can create new files and artifacts, and view them filtered by status and project.
Read more...
In the Application Navigator, right-click the ViewController project and choose New > Web Tier > JSF/Facelets > ADF Task Flow, then click OK.
ADF task flows provide a modular approach for defining control flow in a Fusion web application. Instead of representing an application as a single large JSF page flow, you can break it up into a collection of reusable task flows.
Read more...In the Create ADF Task Flow dialog, enter or select the following values:
| Field or Option | Value |
|---|
| File Name | train-flow.xml |
| Create as Bounded Task Flow | selected |
| Create with Page Fragments | selected |
| Create Train | selected |
A train represents a progression of related activities that guides an end user to the completion of a task.
Read more...Click
OK.
By default JDeveloper displays the new bounded task flow in the diagrammer.
Only a bounded task flow that specifies the
element in its metadata can be used to define a train task flow.
Read more...In the Component Palette,
ADF Task Flow page,
Components panel, drag and drop
View on the diagrammer, then rename the activity. Do this four times, using the following activity names:
start
addresses
payment
review
The red error icons on the diagram indicate that the view activities are not yet associated with any physical page files.
Read more...Drag and drop
Task Flow Return on the diagram. Accept the default name of
taskFlowReturn1.
In the Component Palette, click
Control Flow Case. On the diagram, click the
review icon, then click the
taskFlowReturn1 icon. Rename the control flow case element to
commit.
Like any bounded task flow diagram, you use a task flow return activity to indicate an exit point for the train flow and return control back to the caller.
Read more...In the Structure window, expand
view - start. Right-click
train-stop and choose
Insert Inside train-stop > Display Name.
In the Property Inspector, enter
Start in the
Display Name field.
Repeat the procedure in steps 7 and 8 to add train stop display names to the remaining three view activities, using the following Display Name values:
Addresses
Payment
Review
In the Application Navigator, right-click the ViewController project and choose New > Web Tier > JSF/Facelets > ADF Task Flow, then click OK.
In the Create ADF Task Flow dialog, enter or select the following values, then click OK.
| Field or Option | Value |
|---|
| File Name | childtrain-flow.xml |
| Create as Bounded Task Flow | selected |
| Create with Page Fragments | selected |
| Create Train | selected |
The
element is automatically added for you by JDeveloper when you check the
Create Train box in the Create Task Flow dialog.
Read more...In the Component Palette, drag and drop
View on the diagrammer, then rename the activity to
billing. Repeat the procedure to add one more view activity, using the name
shipping.
Drag and drop
Task Flow Return on the diagram. Change the name to
childFlowReturn1.
Draw a
Control Flow Case from
shipping to
childFlowReturn1. Rename the case element to
done.
In the Structure window, expand view - billing. Right-click train-stop and choose Insert Inside train-stop > Display Name. In the Property Inspector, enter Billing in the Display Name field.
Repeat the procedure in step 15 to add a display name to the remaining view activity, using theDisplay Name value Shipping.
Click
Save All to save your work.
When you complete the steps for creating two bounded task flows as trains, the
ViewControllerproject in the Application Navigator should look something like this,
Read more...
In the editor window, click the train-flow.xml document tab to bring the diagram forward. (If not already open, double-click train-flow.xml in the Application Navigator to open the diagram.)
In the Application Navigator, under Page Flows in the ViewController project, drag childtrain-flowto the diagram and then drop it beneath the addresses icon.
A bounded task flow containing a train can use a task flow call activity to invoke a child bounded task flow representing another train.
Read more...On the diagram, right-click the review icon and choose Train > Move Backward.
A task flow call activity acts like a train stop, executing the default activity in the called task flow first. By default all train stops, including task flow calls acting as train stops, behave as sequential.
Read more...Then right-click the
payment icon and choose
Train > Move Backward.
The diagram should now look like this:
In the Component Palette, click
Control Flow Case. On the diagram, click the
childtrain-flowicon, then click the
payment icon. Accept the default element name of
childFlowReturn1.
When you call
childtrain-flow in the parent
train-flow, you have to manually wire a control flow case to return from the child train.
Read more...On the diagram, select the payment icon. In the Property Inspector, Train Stop section, enter falsein the Sequential field.
By default all train stops behave as sequential. In the Property Inspector, you can set the
Sequential option on the view activity for a train stop to specify whether it has sequential or nonsequential behavior.
Read more...In the Structure window, expand
task-flow-call - childtrain-flow. Right-click
train-stop and choose
Insert Inside train-stop > Display Name.
In the Property Inspector, enter Child train in the Display Name field.
Click
Save All to save your work.
In the Structure window of
train-flow.xml, the
task-flow-call - childtrain-flow element should look like this when all its nodes are expanded:
Read more...
In the Application Navigator, right-click the ViewController project and choose New > Web Tier > JSF/Facelets > ADF Page Template, then click OK.
If following along with the example, at this point there are no page fragments in the Application Navigator.
Read more...In the Create ADF Page Template dialog, enter traintemplate.jsf in the File Name field.
Confirm that Facelets is selected as the document type, and Use a Quick Start Layout is not selected.
With the
Facet Definitions tab in front, click
to add a facet. Enter
body in the
Name field, then click
OK.
A page template is a template definition file written in XML.
Read more...At the top of the editor window, click the document tab
traintemplate.jsf to make sure the visual editor is in focus.
In the Component Palette,
ADF Faces page,
Layout panel, drag
Decorative Box and drop it on the blank page in the visual editor.
When you drag the component to the visual editor, you should see a target rectangle with the name
Page Template Def on the page; this means the component you are dragging will be inserted inside that target.
In the Component Palette,
Layout panel,
Core Structure section, drag
Facet and drop it into the
center facet of the decorative box you just added.
Choose
body from the
Facet Name dropdown list, then click
OK.
The
body facet, defined in the page template definition, allows page authors to add their own content when they create their pages or page fragments using the page template.
Click
Save All to save your work.
The visual editor should look similar to this:
This is just an example; it is entirely up to you how you want to arrange your template page layout.
Read more...
In the editor window, click the traintemplate.jsf document tab to make sure the template page is in focus. If necessary, click the Design tab at the bottom to use the visual editor.
In the Component Palette,
ADF Faces page,
General Controls panel,
Location section, drag
Train and drop it into the
top facet of the decorative box component.
When a task flow consists of a set of pages that end users must visit in a particular order, use the ADF Faces Train component to display a progression of the related activities that guides end users to the completion of the task.
Read more...In the Property Inspector of the train component, Common section, choose Expression Builder from the dropdown menu next to the Value field.
The ADF Faces Train component enables end users to navigate through the train stops in an order specified in the underlying train model.
Read more...Expand
ADF Controller Objects | controllerContext | currentViewPort | taskFlowContext. Then select
trainModel and click
OK.
Click
Save All to save your work.
The visual editor should look similar to this:
This is just an example; it is entirely up to you how you want to arrange your page layout, and where you want to place the Train component.
Read more...
In the editor window, click the train-flow.xml document tab to bring the diagram forward.
If following along with the example, at this point there are no page fragments in the Application Navigator.
Read more...On the diagram, double-click a view icon (for example, start) to open the Create ADF Page Fragment dialog.
Accept the default file name (for example, start.jsff) and make sure Facelets is the selected document type.
On the
Page Layout page, select
Page Template and then select
traintemplate from the dropdown list.
Click Managed Bean and then select Do not Automatically Expose UI Components in a Managed Bean.
In the Create ADF Page Fragment dialog, you can optionally specify whether or not components on the page are exposed in a managed bean, to allow programmatic manipulation of the UI components.
Read more...Click
OK.
JDeveloper displays the page fragment in the visual editor. The Train component from the page template should be visible on the page.
In the visual editor, add contents to the page by inserting ADF Faces components into the
body facet. To follow along with the example, in the Component Palette,
ADF Faces page,
Layout panel,
Interactive Containers and Headers section, drag
Panel Header and drop it into the
body facet on the page. Then insert an output text component into the panel header component.
After creating a page fragment based on the template, you can add contents specific to the page you are creating by inserting appropriate ADF Faces components into the
body facet.
Read more...Repeat steps 1 through 7 for each remaining view icon on the train-flow diagram.
After creating all the pages from the
train-flow diagram,
Read more...In the editor window, click the childtrain-flow.xml tab to bring the diagram forward.
Repeat steps 2 through 7 for both view icons on the childtrain-flow diagram to create the page fragments.
In the editor window, click the billing.jsff tab to bring the page forward.
In the Component Palette, ADF Faces page,
General Controls panel,
Location section, drag
Train Button Bar and drop it into the
menuBar facet of the panel header component on the page.
If following along with the example, you would have added the panel header component as described in step 7.
Accept the EL expression of #{controllerContext.currentViewPort.taskFlowContext.trainModel} and click OK.
The Train Button Bar component is bound to the same train model as the Train component on the template.
Read more...In the editor window, click the shipping.jsff tab to bring the page forward.
In the Component Palette,
Layout panel, drag
Panel Group Layout and drop it into the
menuBarfacet of the panel header component.
In the Property Inspector, Common section, select horizontal from the Layout dropdown list.
In the Component Palette,
General Controls panel,
Location section, drag
Train Button Bar and drop it into
af:panelGroupLayout - horizontal in the Structure window.
Accept the EL expression of #{controllerContext.currentViewPort.taskFlowContext.trainModel} and click OK.
In the Component Palette,
General Controls panel, drag
Button and drop it into
af:panelGroupLayout - horizontal in the Structure window.
In the Property Inspector of the button component, Common section, enter Return to parent flow in the Text field. Then select done from the Action dropdown list.
At runtime, after users navigate into the child train flow pages, they need a way to navigate back to a parent train page.
Read more...Click
Save All to save your work.
The buttons on the
shipping.jsff page, which includes a Train Button Bar component with its
Back and
Next buttons, should look similar to this:
The
af:panelGroupLayout component in the Structure window of
shipping.jsff should look like this:
Read more...
In the Application Navigator, ViewController project, double-click adfc-config under Page Flows to open the default page flow diagram.
By default JDeveloper creates an empty unbounded task flow (source file
adfc-config.xml) when you create a Fusion web application using the Fusion Web Application template.
Read more...In the Component Palette,
ADF Task Flow page,
Components panel, click
View then click on the diagram to add a page icon. Change the default page name to
main.
On the diagram, double-click the page icon you just added to open the Create JSF Page dialog.
Select
Facelets as the document type and accept the default file name of
main.jsf.
On the Page Layout page, select Quick Start Layout, then click Browse.
In the Component Gallery, select the
Two Column category on the left. Then on the right, select the fourth type and the fifth layout.
You should see
Two Column Left, Header (Stretched) under
Options on the right.
ADF Faces provides a number of components that you can use to define the overall layout of a page.
Read more...Select
Apply Themes, then click
OK.
The Create JSF Page dialog should now display the quick start layout selection you made:
Click Managed Bean and select Do Not Automatically Expose UI Components in a Managed Bean. Then click OK.
JDeveloper displays the page in the visual editor.
When you use a quick start layout option, JDeveloper adds the components necessary to display the layout.
Read more...If you wish, you may go directly to step 14 to insert the train flow as a region, then run the page. Otherwise you may continue with the optional layout steps 10 through 13.
In the Component Palette,
ADF Faces page,
Layout panel,
Interactive Containers and Headerssection, drag
Panel Accordion and drop it on the
start facet in the visual editor. In the Property Inspector,
Common section, change
DiscloseMany to
true.
In the Structure window, expand
af:panelAccordion. Select the child
af:showDetailItem.
In the Property Inspector, Common section, change the Text value to Browse.
In the Structure window, right-click af:panelAccordion and choose Insert Inside af:panelAccordion > Show Detail Item to add a second pane. In the Property Inspector, Common section, change theText value to Search.
From the Application Navigator, drag the train-flow node under Page Flows and drop it on the centerfacet in the visual editor. From the Create context menu, choose Region.
An ADF region is a UI component whose content is based on a bounded task flow. To use a task flow as an ADF region within a page, the task flow must be a bounded task flow that contains at least one view activity or one task flow call activity to the page where you want to render the ADF region.
Read more...In the editor window, click the adfc-config.xml tab to bring the diagram forward. Right-click the mainpage icon and choose Run.
If the Create Default Domain dialog displays, enter the default password, for example weblogic1, in the Password and Confirm Password fields, then click OK.
When the application is run and the page is first rendered at runtime, the region's content on the page is that of the first view activity on the train-flow diagram:
By default, JDeveloper automatically configures an integrated server named Integrated WebLogic Server that references a user-specific instance of Oracle WebLogic Server bundled with the IDE.
Read more...Click the second train stop Addresses to navigate to the next page in the train flow.
While difficult to notice in this simple example, note that navigation to the Addresses view occurs within a region on the page. The content of the region is updated using partial page rendering (PPR).
The current stop in the train is indicated by the bold stop icon and display name.
Read more...Click the Payment train stop to jump ahead to the third stop without entering the child train flow.
This is possible because you set the third stop as nonsequential.
On the Payment page, click
Addresses again, then click the
Child train stop to enter the child train flow.
You should see the first page of the child train flow. A child train flow has an icon representation of the parent train before and after the child train stops.
Use the Back and Next buttons or the train stops to navigate forward and backward within the child train flow.
On the Shipping page, click the button to return to the parent train flow.
When you exit the child train flow, you should be returned to the Payment page in the parent train.
Read more...
In this tutorial you created a user interface for navigating end users through a multistep process. You learned how to:
- Use JDeveloper wizards and dialogs to create applications, task flows, page templates, and starter pages
- Define bounded task flows as trains and draw train flows
- Invoke another train using a task flow call activity
- Use task flow return activities to return control flow back to the caller
- Use control flow rules to handle control flow when the called train flow completes execution
- Bind an ADF Train component to a train model
- Add an ADF Region to a page
- Use Integrated WebLogic Server to run a Fusion web application
- http://download.oracle.com/docs/cd/E18941_01/tutorials/jdtut_11r2_44/jdtut_11r2_44.html
كل دي مشاكل حقيقية واعرف ناس كتير حصل معاهم اخر موقف ده ، طيب تعالوا نتخيل موضوعين ..الأول ان فيه فريق عمل شغال فى مشروع والفريق بيتكون من 100 developers ويوميا طبعا المشروع بيتوزع اجزائه كل واحد فى اللى شغل فيه وفى نهاية اليوم بيتجمع المشروع كله تاني .. اعتقد ان الفريق ده محتاج فريق تاني معاه كل شغله تجميع المشروع وتركيبه يوميا … اما الثاني انه كتير مننا developers بيحبوا يجربوا يعدلوا جزئية معينة فى مشروع معين او يعنى يعمل new version وممكن لو عمل حاجة غلط يبوظ المشروع كله فبيضطر انه ياخد نسخة من المشروع ويسميها اسم تاني ويشتغل عليها واحيانا بتحصل لغبطة فى الطريقة دي بين الفيرجنز الكتير لانه مش دايما بيطابق كل تعديل فى اخر فيرجن بالفيرجن الرئيسي … طيب كل دي مشاكل حلها انهاردة هاطرحه بشكل عام فى استخدام Revision Control Systems اللى بيستخدمها شركات كتير جدا لتنظيم العملية الى طرحتها دلوقت بسهولة ، تعالوا بقى نتعرف عليه اكتر 
