Right-click on the Model project and select New. This launches the New Gallery dialog.
In the New Gallery dialog select the Business Components category and then the Business Components from Tables item and click OK.

If you need more details regarding building business services please refer to the Creating a Business Model using ADF Business Components . In this section you simply generate a business service and make some small changes to the model, as needed for the tutorial.

Click OK. This launches the Create Business Components from Tables wizard.

The sequence to create the application module components is crutial:

To create the CustomerView:

1. In the Available Objects pane, select CustomerView and move it to the Data Model Window.
2. Select the node ( CustomerView1) you just added to the Data Model pane.
3. Again,in the Available View Objects pane, select the child node ( OrdersView via OrdersCustomer IDFkLink) and move it to the Data Model pane.
4. Select the node ( OrdersView1 via OrderCustomer via OrdersCustomer IDFkLink) you just added to the Data Model pane.
5. Finally, in the Available View Objects pane, select the child node of the OrdersView ( OrderItemView via OrderItemsOrderIdFkLink) and move it to the Data Model pane.
6. In the Data Model pane, it should appear as a grand child of the CustomerView1 instance.

To create the OrderView:

1. In the Data Model Pane, select the application Module name ( MasterDetailDetailAppModule),
2. In the Available View Objects pane, select the OrdersView node and move it to the Data Model pane.
3. A new data model instance is created named, OrdersView2.
4. Select it and in the Available Objects pane, select the child node OrderItemsView via OrderItemsOrderIdFkLink. Move it to the Data Model window.
5. A child instance of OrdersView2 should be created, named OrderItemsView2 via OrderItemsOrderIdFkLink2.

import customerview.FormCustomersView1; //must match package.form for customers
import orderview.FormOrdersView2OrderItemsView2; //must match package.form for orders

These two statements let you create the two forms from the JClient form packages. 
 
 

private FormCustomersView1 customerframe; //must match customer form name
private FormOrdersView2OrderItemsView2 orderframe; //must match orders form name

These statements let you call the constructor for the Customer and Orders forms in the action handlers that you are going to add later.

Choose File | Save All to save all the files. 

private void jButton1_actionPerformed(ActionEvent e)
{

if (customerframe==null)
{ customerframe = new FormCustomersView1();} //must match customer form name

// Create the panel binding for the Customer form.
customerframe.setBindingContext(panelBinding.getBindingContext());

int width = 300;
int height = 300;
customerframe.setSize(width, height); 

// Determine the new location of the window.
int w = customerframe.getSize().width;
int h = customerframe.getSize().height;
Dimension dim = Toolkit.getDefaultToolkit().getScreenSize();
int x = (dim.width-w)/2;
int y = (dim.height-h)/2;

// Move the window.
customerframe.setLocation(x, y);
customerframe.setVisible(true);
}

private void jButton2_actionPerformed(ActionEvent e)
{

if (orderframe==null)
{ orderframe = new FormOrdersView2OrderItemsView2();} //must match orders form name

// Create the panel binding for the Orders form.
orderframe.setBindingContext(panelBinding.getBindingContext());
 

int width = 300;
int height = 300;
orderframe.setSize(width, height); 

// Determine the new location of the window.
int w = orderframe.getSize().width;
int h = orderframe.getSize().height;
Dimension dim = Toolkit.getDefaultToolkit().getScreenSize();
int x = (dim.width-w)/2;
int y = (dim.height-h)/2;

// Move the window.
orderframe.setLocation(x, y);
orderframe.setVisible(true);
}
 
 

Modify the data bindings for the Orders form.
In the Navigator, open the PanelOrdersView2UIModel.xml file and in the Struture pane, double click on OrdersView2Iter, change the name to OrdersView3Iter and select OrdersView1 under CustomerView1.

Make sure to select the iterator binding nest below the CustomerView1 node. When you press OK, a message will popup informing you that the binding will change and it may affect the application. This is not a problem for us.

navBar.setModel(JUNavigationBar.createViewBinding(panelBinding, navBar,
"OrdersView2", null, "OrdersView2Iter"));

to

navBar.setModel(JUNavigationBar.createViewBinding(panelBinding, navBar,
"OrdersView1", null, "OrdersView3Iter")); 
 

This step associates the customer's order instance with the iterator you just created.

Select PanelOrderItemsView2UIModel.xml and double-click on OrderItemsView2Iter: rename it to OrderItemsView3Iter and base it on the OrderItems instance OrderItemsView1.

Make sure to select the iterator binding nest below the CustomerView1 - OrderView1 node. When you press OK, a message will popup informing you that the binding will change and it may affect the application. This is not a problem for us.

navBar.setModel(JUNavigationBar.createViewBinding(panelBinding, navBar,
"OrderItemsView2", null, "OrderItemsView2Iter"));

to

navBar.setModel(JUNavigationBar.createViewBinding(panelBinding, navBar,
"OrderItemsView1", null, "OrderItemsView3Iter")); 

This step associates the customer's order item instance with the iterator you just created.