Oracle Class Introductions, Chris and Ruth

This demonstration shows the structure of the generated ADF Business Components in a model. The diagrams are first reviewed in Designer by dragging the tables onto the server model diagram. The Module structure can then be viewed as a diagram. The application module is made up of the two base table usages and their relationship. They are generated as the Application Module and View Objects in JDeveloper. In JDeveloper, create a new Business Components diagram for the generated output, then select the Entity Objects and drag and drop them onto the Server Model diagram. The demonstration first looks at the View Objects from the module component definitions by dragging the View Objects onto the diagram. Even though you could drag the Application Module components onto the same page as the View Objects, you can also create a new diagram to view the Application Module. The Application Module shows the two view objects and their binding relationship. You can test the application using the diagram’s context menu as well as perform other tasks, such as formatting the diagram.

This demonstration shows how to modify the module definitions before regenerating business components. The demonstration shows how to add a Where Clause and a second base table usage. After adding a second base table, you choose the module component properties for the base table usage and then invoke the properties for the customer base table usage. An additional Where clause is then added to the already generated base table usage. You can also add additional items to the already generated base table usage. After the desired edits and additions are made, the ADF Business Components are regenerated using the Regenerate ADF business Components from Oracle Designer Wizard. After generation, the additional base table usage is shown in the new View Object, the new Where Clause is also appended to the existing Where clause, and the additional View Usage is shown in the Structure Pane. As a last step, the changed business components are tested.

This demo takes you through viewing generated ADF Business Components. You can view the Designer module used in the Module Diagram window, see the generated Entity Object in the Applications navigator, and view the Entity Object attributes, generated from the Designer table, in the Structure pane. Validation rules are generated from the domains associated with columns in Designer and the View Object attributes are generated from the Designer Module Component base table usages. The Application Module is made up of the generated View Objects. The user can review and update the properties of components or add/modify validation rules using the Entity Object Editor. The user can use JDeveloper Tester to preview generated results. You can verify hints and validation is working using the tester.

This demonstration uses the ADF Business Component generator in JDeveloper to generate business components based on a module defined in the Oracle Designer. Modifications made to the module in Designer are captured in the business components in JDeveloper during regeneration. A Designer module is made up of one or more module components. Before you can start the generation, you need to perform a few steps. Using the Edit Base Table area, the user can add or edit Where clauses, Items, Item Names or Display information. The user has to create an application workspace and project and then establish a connection to the Designer repository. The repository is a work area which contains the modules to be generated. Next, you must establish a connection to the database. The Connection Wizard can be used to create a new Designer Workarea Connection. The Generate ADF Business Components from Oracle Designer Wizard is used to generate the business components from the Designer Module definitions. Begin by selecting the module you want to generate, then select a database connection or create a new one, choose the package name for the ADF Business Components, and then click Finish to generate the ADF Business Components. ADF Business Components are then created and added to your project.

This presentation demonstrates how to create a business service data model from an existing web service in a public UDDI. By using the Generate Web Service Stub/Skeleton, classes are automatically generated based on the WSDL. They implement the data model. The demonstration creates a Struts page flow diagram for the application. A welcome page is created as a user interface, an action is created to invoke the web service, and another JSP page shows the results. You can assign the web service activation to the Struts action through the data control palette and edit the JSP page to get the stock symbol. Adding a struts form tag invokes the action. Editing the code can be done by using the property inspector or by changing the code directly. Finally, you get the results of a web service into a JSP by simply dragging and dropping the return value. The user then creates a Struts page flow diagram and adds items by dragging and dropping from the component Palette. Finally, run the completed application on the embedded J2EE container.

This demo begins by creating a new application workspace using the web application template. This creates two new projects, the Model and ViewController. A new EJB Diagram is then created using the Model context menu. EJB’s can be created with the EJB diagram. For entity beans, just drag and drop tables from the database. After the new entity bean is created, a session bean is created that acts as a session façade to the entity bean. Next, a couple of Data Transfer Objects (DTO) are generated for the entity beans. A method is then added to the session bean to retrieve the department’s details. The session bean is then exposed as a business service data control in Oracle ADF. A simple JSP page is then created to access the EJB. Drag and drop session EJBs from the data control palette right into the JSP visual editor to build a UI on top of it. The EJB and the JSP are then run using the embedded J2EE container.

This demonstration proceeds to add a UIX page to the existing Struts diagram. From the Components Palette, a new data page is dragged and dropped onto the struts diagram. By double clicking on the data page note in the struts page flow diagram, the data page is connected to a specific page. This demonstration creates a master/detail UIX page using the built-in many to many display object. Partial page rendering occurs when browsing the departments. Built-in range paging, and built in order by functionality, by clicking on column headings, is also included. You can change the look and feel of the application by simply changing the code. Look and feel can also be switched at runtime.

To develop JSP Interfaces for Oracle ADF Business Components: model Struts page flow, edit JSP pages, drag and drop data binding, add built in data manipulation methods, and implement transaction management. The demonstration uses a data model that is already implemented. Users can create and edit pages that allow the user to change information; commit operations, perform rollbacks, and release.. Navigation buttons are added to scroll through the records set. The details of the Employees table for each department are added to the page; by dragging and dropping the read-only form from the Data Control Palette.. The JSP page is run using the embedded container. Another data page is added to the Struts Page Flow that allows users to edit the details for a specific employee, and a new JSP page is added and formatted. An input form is dragged onto the new page from the Data Control palette and a field is replaced to disable editing of the Department ID. Add a Forward link to define the flow between the pages. Add functionality to allow users to select a specific employee record for editing. A built-in data action adds this functionality. The complete application flow is then run to test. Commit and rollback buttons were also added to the employee form. This is done by dragging and dropping each operation from the Data Control palette onto the page. The application is then run again to test the new buttons.

This demonstration creates a connection to a database, then uses the UML Modeler to define the business service layer. Business components are created based on existing database tables. The demonstration shows how to choose implementation of database access from Java and then edit entity object attributes by adding a validation rule for an attribute declaratively and adding formatting and headings to attributes. Test the business components using a simple swing based tester.

This demonstration created a simple login procedure for a web application using Struts. The application starts with a login page that activates a validation routine that can route either to the application’s menu or to a failure notice. The demonstration begins by creating the Struts Page Flow, edits the JSP pages, concluding by running the Application with the embedded J2EE container. First, create a new web application, creating two projects named Model and ViewController. From the ViewController context menu, create a new Struts page flow diagram. The page flow modeler provides a visual representation of the content. Create three new JSP pages: login, menu, and failure, using the Component Palette. A Forward link was then created between the login and the menu page. Another Forward link is created between the login page and the failure page. The HTML/JSP Visual Editor then designed the pages. The login page was edited and a style sheet was added to the page. The controller layer is set by using the Struts framework to add processing for the login procedure. Adding Struts and HTML components to the page is easy, just drag and drop the components onto the page. A form is added to the page and a login.do attribute is added to the form component. Add a table to the page by dragging and dropping the component from the component palette. A password field and a submit button was added to the login form. The other JSP pages were edited and the Refresh Diagram from All Pages functionality was performed to add page forward links to the diagram. A Page Link was also added from the failure page to the login page. The business logic was added next to the Controller layer. The Controller layer defines the application flow. A Struts form bean is the way information gets passed between the controller and the view layer, so a Struts form bean passes the parameter to the Struts Action. The DynaActionForm type property is added to the newly-created form bean. A new property was then created for the form bean and named password. The next step was to associate the form bean with the action that uses it. The code was then written to implement the Struts Action. The application then runs on the embedded J2EE container.

This demonstration illustrated database modeling features. It began by creating a new diagram from the Project context menu and creating a database connection. After the database connection is made, the desired tables were selected and dragged and dropped onto the diagram. The user can fine tune the layout of the diagram using options available on the context menu of the diagram window. Offline tables are created after dragging and dropping the tables onto the diagram. Add objects to the diagram using the Component Palette. Generate SQL scripts for existing tables, including DDL operations. You can generate DDL operations SQL scripts by using the “Generate SQL from Offline Database Objects” wizard. This wizard can be used to create online database objects from the offline objects in the project or update objects in your database from your offline dataset object definitions. The SQL scripts made from the wizard are executed using the context menu in the Applications navigator. The database connection navigator reveals the SQL script updates.

The Java Class Modeler demonstration used Java files generated by JDeveloper to create a Java client for a Google Search Web service based on a Google API WSDL. The first thing done to create a Java class model is to create a diagram of the package. Drag and drop the package onto the diagram and drill down from the context menu of the package to visualize the classes within the package. You can also drag and drop the classes directly onto the diagram. There are many different JDeveloper styles of diagram auto layout that can be used to layout your diagram to your satisfaction. The Java Class Modeler automatically synchronizes the diagram and the code, so your changes will show up in both places at the same time. The demonstration shows how to add a new method in one of the classes by editing the class directly from the diagram. The Structure Pane shows the newly added method. Double-click on the new method in the structure pane, and you can navigate to the location where the new method exists. Then add the code for the new method. The demonstration continued by showing how to refractor a class that has changed. Refactoring identifies the dependencies, implements the changes and recompiles the project so that all the attributes and methods in the project that reference a changed class will be updated. A diagram can display more than one package and dependencies can be drawn between packages. Additional packages can be added to the diagram by dragging and dropping the package from the Applications Navigator to the diagram. A dependency is chosen from the component palette and drawn between the packages. The demonstration closed with a display of how to publish the diagram in JavaDoc HTML form. Click the index.html document in the Applications Navigator to open the JavaDoc and navigate through the code documentation and the diagrams.

This UML Activity Modeling demonstration sets up an order management business process. Beginning with a visual representation of the process to add Swimlanes to show separate processes or activities, an activity is then added to the Swimlane. Adding the activity results in a new object flow state. The demonstration shows how to create the transitions that connect the activity and state with the rest of the pre-existing model. You can also create an AND join between activities. An object flow state outcome was created by dragging and dropping the desired flow state onto the diagram from the Structure Pane. Flow states form a structure within an object. The flow state was completed by adding a final state. Guard conditions were added to an already existing OR decision point. Multiple additional refinements can be added to the activity model.

The UML Use Case Modeling demonstration has three steps: creating a visual diagram, adding requirement details in HTML, and publishing the specification in JavaDoc. Modeling cases allow the user to capture the requirements of the system in terms of the functionality it offers to external actors (people, organizations, or software systems). The fully dressed option is used when a use case needs a lot of detail because this template uses more details. The properties menu for the use case adds requirement details in the HTML editor. The fully dressed template appears and the user modifies the template as desired to add requirements. Another use case was added during the demonstration, but less detail was required so a casual use case was selected from the component palette. As with the UML Class Modeler, the UML Use Case Modeler allows you to easily clean up formatting by using auto-layout, align and distribute functions. Notes can be added to the diagram and links to external documents. The demonstration ended by publishing the diagram in JavaDoc HTML form and placing it on a server for reference and validation

There are three steps to UML Class Modeling: Creating the UML Class Model, Transformation and Linking, and Document Generation. UML class modeling lets you capture requirements in a visual model to validate user requirements and document complex applications. This demonstration models the components of a simple order entry application in an abstract UML class diagram and then generates a Java class diagram and implementation files. A basic class diagram is created with some classes and associations between them. Attributes and operations can be added directly onto the diagram screen or by using the class dialog. Formatting the diagram can be accomplished by using the Align and Distribute functionalities. There are several auto-layout options. JDeveloper supports Model Driven Architecture (MDA) style transformations between a UML analysis model and a Java or ADF business components design model. The demonstration showed how to transform the UML analysis model into a visual Java design model and implementation files which show the properties of the UML analysis model. The associations are implemented as Java references. By going directly to the code from the Java class diagram you can add method bodies and more implementation functionality. You can also link the diagrams to move between the different models quickly. Next we are shown how to create the link between the two different design models. UML models can be published as graphic files or inserted in a JavaDoc HTML document. In conclusion, the demonstration showed how to generate the HTML index file, look at the JavaDoc in the browser, and toggle between the two design models.

This demonstration describes how to use the defined schemas to build instance documents. The instance document is built in a new project. JDeveloper requires a schema to be registered. The registration process is done from the Preferences panel. Associate the schema with an extension for the future instance documents. After the schema is registered, the demonstration created an xml document matching the definition of the schema that was just registered. The first thing to do is to add a root to the empty document. The next thing to do is to mention the namespaces to work with. After that, elements are added. Since the schema is registered, the document can be validated against the schema. Errors are reported in the Messages pane. Registering the schema also offers the possibility of using the component palette to manipulate XML Elements. You can drag and drop elements from the component palette directly into the code pane.

Schemas are opened in JDeveloper using the XML Schema Visual Editor. You can view the source by clicking the Source tab at the bottom of the Editor Pane. Several panels of JDeveloper are synchronized when you use the XML Schema Visual Editor: the visual editor and code editor panel, the schema component palette, the property inspector, and the structure window. This demonstration describes the basic artifacts of the XML Schema Editor. Artifacts are called ComplexType or SimpleType.. Another artifact represents an Element. Subcomponents can be expanded or collapsed by clicking on the plus or minus sign next to the object. Other types of objects are represented with white backgrounds. Attributes represented in the Editor. Mandatory attributes are shown with a red star in front of their name. One artifact represents a sequence. The cardinalities are visually represented in three ways – explicitly, graphically, and in the property inspector. Graphical representations are available from the schema components palette. You can control the visual editor in different ways. There is a grab scroll to use in the XML Schema visual editor. You can zoom in and out. After selecting a node in the editor, you can collapse or expand its subcomponents. When you open an existing schema, it is opened in JDeveloper using the XML Schema Visual Editor. You can view the code by switching to the Source tab. In the editor, these panels are synchronized: The Visual Editor, the Schema Components Panel, the Property Inspector and the Structure Pane.

Building the view based on ADF UIX technology begins with the Data Page node - /Main in the Struts page flow. The user then can wire the Data Page to a specific page. The name of the page will be synchronized with the data page action node by default and, depending on technologies selected for the project; there may be a list of available file types. This demonstration creates a master/detail page using the new data control palette. Two data bound items are created on the page – one master form and one detail table. The demonstration shows how selecting an item in the struts page flow shows the item’s properties in the Property inspector. Also, the structure window is in sync with the selection. The demonstration then adds a delete button so the user can delete records from the details item. A Submit button is then added so the user can navigate to another page. You do this by specifying an event that sends an event result to the Struts controller. The demonstration then creates an input form. ADF UIX has a set of components to help with laying out the page. You can look at Named Children as slots where you can add components. You can edit the page in the XML code editor and preview the page by clicking on the Preview tab. The application is then run. ADF UIX has another feature to assist in building applications called partial page rendering (PPR).

ADF JClient in JDeveloper 10g supports declarative development of Rich Client application. This demonstration is an example of how to develop a master/detail JClient application using ADF business components. First you create an empty JClient form. You start your application by using the ADF JClient template which creates a view specific for building JClient applications. Swing components in ADF JClient are bound to business services like ADF business components by using the data control palette. The demo first creates three data bound text fields to show the customer account information and then creates labels from hints in the business component view object. Then format the fields by aligning them and adding labels as well as adding a scroll bar. A table and a graph component is then created to show the detail data set. And finally the application is run.

We see here how to create a business service data model from an existing web service in a public UDDI. You need a pointer to the WSDL. Classes can be automatically generated based on the WSDL. They implement the data model. The demonstration creates a Struts page flow diagram. A welcome page is created to get a stock parameter from the user, an action is created to invoke the web service, and another JSP page shows the results. You can assign the web service activation to the Struts action through the data control palette and then edit the JSP page to get the stock symbol. Adding a struts form tag invokes the action. Editing the code can be done in several ways – by using the property inspector or change the code directly. Finally, you get the results of a web service into a JSP by simply dragging and dropping the return value. You then run the completed application on the embedded J2EE container. This functionality can be used for any application where you want input from the user and your application then returns a value.

The Apache Struts Page Flow can be opened directly by editing the struts_config.xml file directly or by using the Open Struts Page Flow context menu on any project with the Struts technology scope enabled. You can edit and document your page flow using the Page Flow Diagram. The shapes on the diagram represent Actions, Page Forward Actions and Data-bound pages. The solid lines are Action Forward, defined in the Struts XML. The Dashed lines represent explicit links between pages or pages and actions. Form-Bean usage is indicated by an overlay icon. The diagram gives you several ways to visualize and navigate large flows: thumbnail view, and zoom in/out controls. You can customize color and font on the diagram and add notations. You can use the Source view to see the Struts XML configuration file. This is fully synched with the diagram view and you may edit the Struts definition in either view. The view insight gives the user code insights and syntax highlights to reduce manual coding errors. The JDeveloper property inspector can be used to edit Struts metadata. You can create new Struts elements in the Structure view or using the component palette. Items with a warning indicate that there is no code or page associated with them.

Developing Business Services with Oracle ADF Business Components is accomplished in four steps: Modeling Business Components, adding Validation Rules, adding Formatting Rules, and testing with a Swing Based Tester. This demonstration begins by creating a connection to a database, then using the UML Modeler to define the business service layer. Business components are created based on existing database tables. The demonstration shows how to implement database access from Java and then edit entity object attributes by adding validation rules, formatting and headings to attributes. Testing the business components using a simple swing based concluded the demonstration.

Introducing Oracle 10g JDeveloper TopLink Mapping editor. Begin by creating a new Java class diagram. JDeveloper creates a new diagram and adds the diagram to the application model. You then add the database tables to the diagram. JDeveloper will automatically reverse engineer the TopLink mappings from a Java class diagram. The TopLink mapping editor also supports forward engineering and meet in the middle use classes. You just drag the database tables onto the diagram. JDeveloper allows you to create different elements from the tables. In the demonstration, Java classes are created. JDeveloper adds the tables to the diagram, creates all the relationships, created the .Java class files for both tables and added them to the application model. The demonstration then opens the TopLink Mappings editor and reviews the TopLink mappings created by JDeveloper. JDeveloper creates TopLink descriptors for each Java class and maps each attribute. The TopLink Mapping editor also allows you to configure your deployment information and sequencing information.. Custom queries can also be defined and you can query keys for each descriptor. There are several advanced TopLink properties available. The mapping editor provides a mapping report that identifies problems in your model.

You can build business services with Enterprise JavaBeans (EJBs) using Oracle JDeveloper 10g. Create a new application workspace that will use a JSP, struts, and an EJB application template. The application is built using an application template that is configured for building a data-bound web application. It consists of one project for the view and controller components (JSP and Struts) and another project for the data model (EJB).The JSP, Struts, and EJB application template created an application with two projects called Model and ViewController. EJB Modeler allows the user to create a model session, entity, and message driven deans. Users can model session beans, add properties and business methods which are synched with the source files. Users can model entity beans and forward engineer them as database tables or reverse engineer database tables as Container Managed Persistence (CMP) entity beans with a simple drag and drop action. Foreign key relationships in the database are also reverse engineered as Container Managed Relationships (CMRs). You can model the relationships between entity beans or references between EJBs using the EJB Modeler. Adding a reference between EJBs automatically synchronizes the deployment descriptor by generating the appropriate tags with the lookup code in the bean class. JDeveloper provides an easy mechanism to generate Data Transfer Object design pattern for CMP Entity beans. The EJB module editor has a user interface that allows you to edit all the EJBs in the deployment descriptor. The Relationships panel in the editor allows you to add, edit, and delete the CMRs between entity beans intuitively. The Methods panel lets you add, edit, and delete different types of EJB interface methods. The EJB module editor lets you make changes to different types of bean properties. All modifications made in the EJB module editor are synchronized with model, source, and the deployment descriptor. The EJB verifier provides a way to detect deploy-time errors., validates the document type definition (DTD) and verifies the EJB classes for inconsistencies.

It is easy to create a Data Control from a web service and use it in a Struts controlled JSP application. Using a live connection to another company, you can view the WSDL file of a service. You can then create a Data Control for this web service using its context menu. The necessary files are generated into a project you select and the Data Control is displayed in the Data Control Palette which you can use in a Struts Page Flow to build your application page flow. Use a JSP to capture data in a form and insert a Data Page that is bound to a struts action. Then edit the JSP page by adding a struts HTML form that is aware of struts actions. After defining a link from this form to the action, add a text field to the new form and use the Property Inspector to add properties. Assign a name to pass a parameter from the page to the Struts action. Refresh the diagram to display the link. Add the desired operation by dropping the operation onto the action as a method. Use the structure pane and the property inspector to see how the action mapping handled the data control. Now, write expression language to use the parameter created earlier. You can define the JSP page that bound the action. Dragging the return to the diagram generates expression language to do this. Use the features of the Editor to add content and style. Use the embedded OC4J to test your page flow. The web service returns the expected action.

Oracle Application Development Framework (Oracle ADF) is a complete J2EE Framework included with Oracle 10g JDeveloper. Application Templates help customize the IDE and simplify the development environment. Drag and drop Database fields into a UML diagram to create objects. Data model components collect data and present it to the client. The Page Flow Editor allows the user to define the flow of the application. Oracle JDeveloper 10g contains a WYSIWYG editor, (What you see is what you get), to design the user interface. There are several views available including HTML, JSP, ADF UIX, and Swing/ADF Jclient. The Data Control Palette displays all of the previously created Business Services. The embedded Oracle Container for J2EE allows the user to run, tune, and debug an application directly from the IDE.

This tutorial introduces you to the Integrated Development Environment (IDE). We learn about the three windows that appear when first opening JDeveloper – the largest window is referred to as the Visual Editor or Code Editor, the remaining two are the Structure Window, and the Applications Navigator. To get started with JDeveloper, first create a workspace to store your work. To create a workspace, select “Applications” in the Applications Navigator and choose File|New. After the workspace is created, add a project within your workspace and name it. You can choose the default name, or specify a name. The directory name will change automatically to stay in sync with any name you select. A project is a subdivision of a workspace and organizes your work within the workspace. The Application Navigator lists workspaces and projects and their hierarchical contents. The names of the workspaces and projects will appear in italics until saved. This tutorial creates a JSP, an HTML page with embedded Java code. It demonstrates how the structure window synchronizes with other windows and displays the structure of the JSP. The Component Palette and the Property Inspector are explained in detail. You can format the text on your page using the Property Inspector. Choose components you need to create your applications from the Component Palette. You can add style sheets and HTML components. You can split the window to see both the design and source code at the same time. A change made in one window is immediately visible in the other because they are synchronized. You can add code in the source view and the Code insight feature offers suggestions in the correct context. When finished, run the page to see how it will look in a browser window. If your application requires a connection to other machines or devices use the Connection Navigator to create those connections. Create a database connection by using the Connections tab of the Applications navigator.

This tutorial introduces you to the Integrated Development Environment (IDE). We learn about the three windows that appear when first opening JDeveloper – the largest window is referred to as the Visual Editor or Code Editor, the remaining two are the Structure Window, and the Applications Navigator. To get started with JDeveloper, first create a workspace to store your work. To create a workspace, select “Applications” in the Applications Navigator and choose File|New. After the workspace is created, add a project within your workspace and name it. You can choose the default name, or specify a name. The directory name will change automatically to stay in sync with any name you select. A project is a subdivision of a workspace and organizes your work within the workspace. The Application Navigator lists workspaces and projects and their hierarchical contents. The names of the workspaces and projects will appear in italics until saved. This tutorial creates a JSP, an HTML page with embedded Java code. It demonstrates how the structure window synchronizes with other windows and displays the structure of the JSP. The Component Palette and the Property Inspector are explained in detail. You can format the text on your page using the Property Inspector. Choose components you need to create your applications from the Component Palette. You can add style sheets and HTML components. You can split the window to see both the design and source code at the same time. A change made in one window is immediately visible in the other because they are synchronized. You can add code in the source view and the Code insight feature offers suggestions in the correct context. When finished, run the page to see how it will look in a browser window. If your application requires a connection to other machines or devices use the Connection Navigator to create those connections. Create a database connection by using the Connections tab of the Applications navigator.

Oracle Application Development Framework (Oracle ADF) is a complete J2EE Framework included with Oracle 10g JDeveloper. Application Templates help customize the IDE and simplify the development environment. Drag and drop Database fields into a UML diagram to create objects. Data model components collect data and present it to the client. The Page Flow Editor allows the user to define the flow of the application. Oracle JDeveloper 10g contains a WYSIWYG editor, (What you see is what you get), to design the user interface. There are several views available including HTML, JSP, ADF UIX, and Swing/ADF Jclient. The Data Control Palette displays all of the previously created Business Services. The embedded Oracle Container for J2EE allows the user to run, tune, and debug an application directly from the IDE.

JDeveloper is a completely integrated development environment for multiple languages such as Java and PL/SQL. The development life cycle for an enterprise system includes modeling, coding, versioning, debugging, tuning, testing, and deploying the final product. This tutorial shows you how to add new business service entities with the Component Palette or the Database Navigator, with drag-and-drop. You can build validation rules for data entry directly in JDeveloper. The user can develop user interfaces for applications using Business Services. There is a visual Page Flow diagrammer used to visually construct the page flow of Struts applications. Oracle ADF has a databinding layer to help with binding applications to Business Services simply by dragging and dropping. To make testing easier, JDeveloper has an Application Server – the OC4J. This feature reduces time spent editing, compiling and testing. It contains a whole suite of testing and tuning tools such as a debugger, profilers, audits/metrics and a CodeCoach. These testing tools help a developer improve code quality and performance. The user can also customize JDeveloper by turning off some features not being used and develop custom file extensions. JDeveloper has default application templates or you can create your own custom templates. Templates help set defaults for the applications you build. Technology Scope filters the contents of the new gallery and provides prompts with the menu choices you’re most likely to need. JDeveloper also includes an XML schema editor the user interacts with through the structure window, component palette, and property inspector. You can also work with database objects in any SQL92-compliant database and use the SQL Worksheet to tune and execute SQL statements. You can work with database diagrams to edit existing tables and create new tables as well as generate DDL operations from the database diagram.