Identify the types of components that cooperate to provide the business service implementation
An entity object represents a row in a database table and simplifies modifying its data by handling all data manipulation language (DML) operations for you. It can encapsulate business logic to ensure that your business rules are consistently enforced. You associate an entity object with others to reflect relationships in the underlying database schema to create a layer of business domain objects to reuse in multiple applications. A view object represents a SQL query and simplifies working with its results. You use the SQL language to join, filter, sort, and aggregate data into the shape required by the end-user task being represented in the user interface. This includes the ability to link a view object with other entity objects to create master-detail hierarchies of any complexity. When end users modify data in the user interface, your view objects collaborate with entity objects to consistently validate and save the changes. An application module is the transactional component that UI clients use to work with application data. It defines an updateable data model along with top-level procedures and functions (called service methods) related to a logical unit of work related to an end-user task. | |
[ ] |
Explain how ADF BC components are used in a Web Application
http://download.oracle.com/docs/cd/E15523_01/web.1111/b31974/bcdcpal.htm#BBJBDCHF |
Querying and Persisting Data | |
[ ] | Describe the characteristics of an ADF BC view object |
[ ] | Create a view object that can be used for performing a query in a Web application |
[ ] | Define a SQL statement on which to base a query for a view object |
[ ] | Explain how entity objects relate to database tables |
[ ] | Describe the persistence mechanism of entity objects |
[ ] | Use the Create Entity Object wizard to generate entity objects from database tables |
[ ] | Create associations between entity objects to represent business relationships |
[ ] | Create updatable view objects based on entity objects |
[ ] | Link view objects to one another in a master-detail hierarchy |
[ ] | Refactor objects in an application |
Exposing Data to Clients | |
[ ] | Explain the role of application modules |
[ ] | Describe the characteristics of application modules |
[ ] | Use the Create Application Module wizard to define the data model for an application module |
[ ] | Explain how application modules can manage business components transactions |
[ ] | Explain how application modules can manage application stateE |
[ ] | Explain the role of the ADF Model |
Declaratively Customizing Data Services | |
[ ] | Declaratively change data behaviour |
[ ] | Declaratively modify the default behavior of view objects, entity objects, and application modules |
[ ] | Define a view accessor for a list of values(LOV) |
[ ] | Define a list of values (LOV) for an attribute |
Programmatically Customizing Data Services | |
[ ] | Generate Java classes for business components to modify default behavior programmatically |
[ ] | Override class methods to change or augment default behavior |
[ ] | Modify the WHERE clause of a view object at run time |
[ ] | Explain the benefits of adding service methods at the application module level (rather than at the view level) |
[ ] | Create a test client for testing your custom code |
[ ] | Modify a view object's client code to add a new employee to the employees view object |
Validating User Input | |
[ ] | Describe the types of validation available for ADF applications |
[ ] | Evaluate which validation options are appropriate for different validations |
[ ] | Add declarative validation for an entity object |
[ ] | Identify the other non-declarative validation options and when they might be used |
[ ] | Describe the benefits of using domains for validation |
Troubleshooting ADF BC Applications | |
[ ] | Identify the JDeveloper tools for logging and diagnostics |
[ ] | Use Java code auditing tools |
[ ] | Make use of FileMon and Junit to debug an application |
[ ] | Use the JDeveloper profiler |
[ ] | Use the JDeveloper debugger |
[ ] | Identify sources of Help |
Understanding UI Technologies | |
[ ] | Describe the use of Web browsers and HTML |
[ ] | Explain how Java has come into widespread use as a language for developing Web applications |
[ ] | Describe the function of Servlets and JSPs |
[ ] | Define JavaServer Faces |
[ ] | Explain the JSF component architecture |
[ ] | Expalin some JSF component types included in the standard implementation |
[ ] | Describe the purpose of backing beans |
[ ] | Describe the JSF life cycle |
[ ] | Explain how ADF Faces augments the JSF life cycle |
Binding UI Components to Data | |
[ ] | Create an empty JSF page |
[ ] | Use three different ways to add ADF Faces UI components to a page |
[ ] | Describe the types of data-bound components that can be added to a JSF page |
[ ] | Describe the structure of an EL (Expression Language) expression |
Planning the User Interface | |
[ ] | Describe the Model-View-Controller design pattern |
[ ] | Differentiate between bounded and unbounded task flows |
[ ] | Create task flows to define control flow in an application |
[ ] | Specify control flow rules |
[ ] | Define global navigation |
[ ] | Use routers to declaratively route control flow to activities based on an EL expression |
[ ] | Define the role of managed beans in task flows |
[ ] | Explain the types of validation available in the user interface |
Adding Functionality to Pages | |
[ ] | Internationalize the user interface so that the application can be used in multiple locales |
[ ] | Use component facets to specify subordinate elements such as toolbars, headers and footers |
[ ] | Implement a list of values (LOV) to enable users to select a value from a list |
[ ] | Add a calendar component to an input date field to make it easy for users to select a date |
[ ] | Use the table component to display structured data as a formatted table |
[ ] | Employ the tree component to display hierarchical data |
[ ] | Add icons and images to an application with ADF Faces output componentsE |
[ ] | Create Search forms using the ADF query component |
[ ] | Use ADF Data Visualization components to add charts, graphs, map etc to your JSF pages |
Implementing Navigation on Pages | |
[ ] | Implement command buttons and links |
[ ] | Create menus - Menu bar |
[ ] | Create menus - Popup |
[ ] | Create menus - Context |
[ ] | Use a navigation page |
[ ] | Use breadcrumbs |
[ ] | Create trains |
Achieving the Required Layout | |
[ ] | Build complex page layouts with layout components |
[ ] | Explain the role of ADF Faces skins |
[ ] | Use dynamic page layout |
Ensuring Reusability | |
[ ] | Identify the benefits of reusing components |
[ ] | Create a resource catalog to enable sharing of resources within and across teams and applications |
[ ] | Create ADF libraries to share components within and across teams and applications |
[ ] | Create a task flow template for reuse across different bounded task flows |
[ ] | Create a page template for reuse across the JSF pages in an application to enable a consistent look and feel |
[ ] | Create a declarative component for reuse in different pages of an application |
[ ] | Create a page fragment to use in multiple pages of the application |
[ ] | Employ a bounded task flow as a region in a JSF page |
Passing Values between UI Elements | |
[ ] | Evaluate whether the data model contains opportunities to reduce the need for passing values between pages |
[ ] | Use a managed bean to pass values between JSF pages |
[ ] | Store values in memory-scoped attributes to hold and pass information between pages and life cycle phases |
[ ] | Use parameters to pass information to different parts of the application |
Responding to Application Events | |
[ ] | Configure managed beans to contain code to respond to events |
[ ] | Explain the different types of events |
[ ] | Use phase listeners to listen for and respond |