Oracle software implements the standards of the Web Content Accessibility Guidelines (WCAG) 1.0 Level AA using an interpretation of the standards at http://www.oracle.com/accessibility/standards.html

ADF Faces user interface components have built-in accessibility support for visually and physically impaired users. User agents such as a web browser rendering to nonvisual media such as a screen reader can read component text descriptions to provide useful information to impaired users. Access key support provides an alternative method to access components and links using only the keyboard. ADF Faces accessibility audit rules provide direction to create accessible images, tables, frames, forms, error messages and popup windows using accessible HTML markup.

For information on how to develop accessible ADF Faces pages, see Developing Accessible ADF Faces Pages in Developing Web User Interfaces with Oracle ADF Faces.

<?xml version= '1.0' encoding= 'UTF-8' ?>
<xs:schema targetNamespace="http://example.com/grades"
        xmlns:xs="http://www.w3.org/2001/XMLSchema"     
        xmlns:tns="http://example.com/grades"
        attributeFormDefault="qualified" elementFormDefault="qualified" 
        xmlns:xjc="http://java.sun.com/xml/ns/jaxb/xjc" 
        xmlns:jaxb="http://java.sun.com/xml/ns/jaxb"
        jaxb:extensionBindingPrefixes="xjc" 
        jaxb:version="2.0">        
        
    <xs:element name="TestScore">
        <xs:complexType>
            <xs:sequence>
                <xs:element name="name" type="xs:string"/>
                <xs:element name="testName" type="xs:string"/>
                <xs:element name="testScore" type="xs:double"/>
                <xs:element name="testCurve" type="xs:double"/>
            </xs:sequence>
        </xs:complexType>
    </xs:element>
    <xs:element name="TestGrade">
        <xs:complexType>
            <xs:sequence>
                <xs:element name="grade" type="tns:Grade"/>
            </xs:sequence>
        </xs:complexType>
    </xs:element>
    <xs:simpleType name="Grade">
        <xs:restriction base="xs:string">
            <xs:enumeration value="A"/>
            <xs:enumeration value="B"/>
            <xs:enumeration value="C"/>
            <xs:enumeration value="D"/>
            <xs:enumeration value="F"/>
        </xs:restriction>
    </xs:simpleType>
</xs:schema>

1. Save the schema file as shown in example grades.xsd schema to a local file named grades.xsd.
2. In the Application Navigator select the Grades project.
3. Right-click and in the context menu select New....
4. In the New Gallery select the All Technologies tab.
5. In the Categories area, expand General and select XML.
6. In the Items area, select XML Schema. Click OK.
7. In the Create XML Schema dialog, in the File Name field enter grades.xsd.
8. In the Create XML Schema dialog, in the Directory field add the xsd directory to the Grades project path name, as shown in Figure 9-4.

   Figure 9-4 Adding Schema to Grades Project in xsd Directory

   
   Description of "Figure 9-4 Adding Schema to Grades Project in xsd Directory"

   Click OK.

9. In the grades.xsd file, select the Source tab.
10. Copy the schema shown in example above to the grades.xsd in the Grades project, as shown in Figure 9-5.

    Figure 9-5 Shows the Grades.xsd Schema File in the Grades Project

    
    Description of "Figure 9-5 Shows the Grades.xsd Schema File in the Grades Project"

1. In the Application Navigator, select the Grades project.
2. Right-click and in the context menu select New.... and select the All Technologies tab.
3. In the New Gallery, in the Categories area, expand Business Tier and select Business Rules.
4. In the New Gallery, in the Items area, select Business Rules. Click OK.

   Oracle JDeveloper displays the Create Business Rules dialog, as shown in Figure 9-6.

   Figure 9-6 Adding a Business Rule to Grades with the Create Business Rules Dialog

   
   Description of "Figure 9-6 Adding a Business Rule to Grades with the Create Business Rules Dialog"
5. In the Name field, enter a name to name the dictionary. For example, enter GradingRules.
6. To add an input, from the list next to the Add button select Input....
7. In the Type Chooser, expand the Project Schemas Files folder and expand grades.xsd. Select the input TestScore, as shown in Figure 9-7.

   Figure 9-7 Shows the Type Chooser Dialog with TestScore Element

   
   Description of "Figure 9-7 Shows the Type Chooser Dialog with TestScore Element"
8. On the Type Chooser window, click OK. This displays the Create Business Rules dialog.
9. In the Create Business Rules dialog, in a similar manner to the input add the output by selecting Output... to add the output element TestGrade from the grades.xsd schema.

   The resulting Create Business Rules dialog is shown in Figure 9-8.

   Figure 9-8 Create Business Rules Dialog with Grades Input and Output

   
   Description of "Figure 9-8 Create Business Rules Dialog with Grades Input and Output"

   Click OK. Oracle JDeveloper creates the GradingRules dictionary as shown in Figure 9-9.

10. In the File menu, select Save All to save your work.

Figure 9-9 Shows the New Grading Rules Dictionary

Description of "Figure 9-9 Shows the New Grading Rules Dictionary"

Note that the business rule validation log area for the new dictionary shows several validation warnings. These validation warning messages are cleared as you modify the dictionary in later steps.

1. In Rules Designer, select the Value Sets navigation tab.
2. From the list next to the Create Value Set... button, select List of Ranges.
3. For the value set, double-click in the Name field to select the default name.
4. Enter Grade Scale, and press Enter to accept the value set name.
5. In the Value Set table, double-click the icon for the Grade Scale value set to display the Edit Value Set dialog.
6. In the Edit Value Set dialog, click Add to add a value and click Add three times to add three more values.
7. In the Endpoint field, enter 90 for the top endpoint and press Enter to accept the new value.
8. For the next value, in the Endpoint field enter 80 and press Enter to accept the new value. Similarly, for the next two values enter values in the Endpoint field, values 70 and 60.
9. In the Included Endpoint field for each value select each check box.
10. Modify the Alias field for each value to enter the values A, B, C, D, and F, for each corresponding range, (press Enter after you add each alias).

1. In Rules Designer, select the Facts navigation tab.
2. In the Facts navigation tab select the XML Facts tab.
3. Double-click the XML fact icon for the TestScore fact. This displays the Edit XML Fact dialog.
4. In the Edit XML Fact dialog select the testScore property.
5. In the Value Set field, from the list select Grade Scale.
6. Click OK.

1. In Rules Designer, select Ruleset_1 under the Rulesets list.
2. In Ruleset_1, click Create from the Decision Table area on the Overview tab. This creates DecisionTable_1. You can ignore the warning messages shown in the Business Rule Validation log area. You remove these warning messages in later steps.
3. In the Decision Table, DecisionTable_1, click the Add button and from the list select Condition.
4. In the Decision Table, double-click <edit condition>. Then, in the variables navigator expand TestScore and select testScore. This enters the expression TestScore.testScore for condition C1.

1. In the Decision Table, click the Add button and from the list select Action and select Assert New.
2. In the Actions area, double-click Assert New.

   This displays the Action Editor dialog.

3. In the Action Editor dialog, in the Facts area select TestGrade.
4. In the Action Editor dialog, in the Properties table for the property grade, select the Parameterized check box and the Constant check box.

   This specifies that each rule independently sets the grade.

5. In the Action Editor dialog select the Always Selected check box.
6. In the Action Editor dialog click OK.
7. Select Save All from the File main menu to save your work.

You can use the Decision Table split operation to create rules for the value set associated with the conditions row in the Decision Table. This creates one rule for every value.

To split the decision table, from the Decision Table, click the Split Table button from the list select Split Table. The split operation eliminates the "do not care" cells from the table. The table now shows five rules that cover all ranges, as shown in Figure 9-10.

These steps produce validation warnings for action cells with missing expressions. You fix these problems in later steps when you define actions for each rule.

Figure 9-10 Splitting a Decision Table Using Split Table Operation for Grades

Description of "Figure 9-10 Splitting a Decision Table Using Split Table Operation for Grades"

1. In the Actions area, double-click the action cell for rule R1 as shown in Figure 9-11.

   Figure 9-11 Adding Action Cell Values to Grades Decision Table

   
   Description of "Figure 9-11 Adding Action Cell Values to Grades Decision Table"
2. In the list select the corresponding value for the action cell. For example, select Grade.F.
3. For each of the remaining action cells select the appropriate value for TestScore: D, C, B, and A.

1. In the Application Navigator, in the Grades project, expand the Resources folder and double-click the dictionary GradingRules.rules.
2. Select the Decision Functions navigation tab.
3. In the Name field in the Decision Functions table edit the decision function name to enter the value GradesDecisionFunction, and then press Enter, as shown in Figure 9-12.

Figure 9-12 Renaming Decision Function in Rules Designer

Description of "Figure 9-12 Renaming Decision Function in Rules Designer"

1. In the Application Navigator, select the Grades project.
2. Right-click the Grades project and in the context menu select New....
3. In the New Gallery, select the All Technologies tab.
4. In the New Gallery, in the Categories area expand Web Tier and select Servlets.
5. In the New Gallery, in the Items area select HTTP Servlet. Click OK.

   Oracle JDeveloper displays the Create HTTP Servlet Welcome page.

6. Click Next.

   This displays the Web Application page.

7. Select Servlet 2.5\JSP 2.1 (Java EE 1.5) and click Next.

   This displays the Create HTTP Servlet - Step 1 of 3: Servlet Information page.

8. Enter values in Create HTTP Servlet - Step 1 of 3: Servlet Information page, as follows, and as shown in Figure 9-13.

   • Class: GradesServlet

   • Package: com.example.grades

   • Generate Content Type: HTML

   • Generate Header Comments: unchecked

   • Implement Methods: service() checked and all other check boxes unchecked

   Figure 9-13 Create HTTP Servlet Wizard - Step 1 of 3: Servlet Information

   
   Description of "Figure 9-13 Create HTTP Servlet Wizard - Step 1 of 3: Servlet Information"

   Click Next.

   This displays the Create HTTP Servlet: Step 2 of 3: Mapping Information dialog as shown in Figure 9-14.

   Figure 9-14 Create HTTP Servlet Wizard - Step 2 of 3: Mapping Information

   
   Description of "Figure 9-14 Create HTTP Servlet Wizard - Step 2 of 3: Mapping Information"
9. Configure this dialog as follows:

   • Name: GradesServlet

   • URL Pattern: /gradesservlet

   Click Finish when done.

   JDeveloper adds a Web Content folder to the project and creates a GradesServlet.java file and opens the file in the editor as shown in Figure 9-15.

   Figure 9-15 Generated GradesServlet.java

   
   Description of "Figure 9-15 Generated GradesServlet.java"
10. Replace the generated servlet with the source as shown in the grades application example below.

    package com.example.grades;
     
    import java.io.IOException;
    import java.io.PrintWriter;
     
    import java.util.ArrayList;
    import java.util.List;
     
    import javax.servlet.ServletConfig;
    import javax.servlet.ServletException;
    import javax.servlet.http.HttpServlet;
    import javax.servlet.http.HttpServletRequest;
    import javax.servlet.http.HttpServletResponse;
     
    import oracle.rules.rl.exceptions.RLException;
    import oracle.rules.sdk2.decisionpoint.DecisionPoint;
    import oracle.rules.sdk2.decisionpoint.DecisionPointBuilder;
    import oracle.rules.sdk2.decisionpoint.DecisionPointInstance;
    import oracle.rules.sdk2.exception.SDKException;
    import oracle.rules.sdk2.repository.DictionaryFQN;
     
    public class GradesServlet extends HttpServlet {
     
        private static final String CONTENT_TYPE = "text/html";
        private static final String DICT_PKG = "com.example.grades";
        private static final String DICT_NAME = "GradingRules";
        private static final DictionaryFQN DICT_FQN =
            new DictionaryFQN(DICT_PKG, DICT_NAME);
        private static final String DF_NAME = "GradesDecisionFunction";
     
        private DecisionPoint m_decisionPoint = null; // init in init()
     
        public void init(ServletConfig config) throws ServletException {
            super.init(config);
            
            try {
                
                // specifying the Decision Function and Dictionary FQN
                // load the rules from the MDS repository.
                m_decisionPoint = new DecisionPointBuilder()
                                    .with(DF_NAME)
                                    .with(DICT_FQN)
                                    .build();
            } catch (SDKException e) {
                System.err.println("Failed to build Decision Point: " +
                                   e.getMessage());
                throw new ServletException(e);
            }
        }
     
        public void service(HttpServletRequest request,
                            HttpServletResponse response) throws ServletException,
                                                                 IOException {        
            // retrieve parameters
            String name = request.getParameter("name");
            String strScore = request.getParameter("testScore");
     
            // open output document
            StringBuilder doc = new StringBuilder();        
            addHeader(doc);
     
            // create TestScore object to assert
            final TestScore testScore = new TestScore();
            testScore.setName(name);
            
            try {
                testScore.setTestScore(Integer.parseInt(strScore));
            } catch (NumberFormatException e){ /* use default val */ }                
     
            // get DecisionPointInstance for invocation
            DecisionPointInstance point = m_decisionPoint.getInstance();
            
            // set input parameters
            point.setInputs(new ArrayList() {{ add(testScore); }});
     
            // invoke decision point and get result value
            TestGrade testGrade = null;        
            try {
                
                // invoke the decision point with our inputs
                List<Object> result = point.invoke();
                if (result.size() != 1){
                    error(doc, testScore.getName(), "bad result", null);                
                }
                // decision function returns a single TestGrade object
                testGrade = (TestGrade)result.get(0);
            } catch (RLException e) {
                error(doc, testScore.getName(), "RLException occurred: ", e);
            } catch (SDKException e) {
                error(doc, testScore.getName(), "SDKException occurred", e);
            } 
            
            if (testGrade != null){
                // create output table in document
                openTable(doc);
                addRow(doc, testScore.getName(), strScore, testGrade.getGrade());
                closeTable(doc);
            }
     
            addFooter(doc);
     
            // write document
            response.setContentType(CONTENT_TYPE);
            PrintWriter out = response.getWriter();
            out.println(doc);
            out.close();
        }
     
     
        public static void addHeader(StringBuilder doc) {
            doc.append("<html>");
            doc.append("<head><title>GradesServlet</title></head>");
            doc.append("<body>");
            doc.append("<h1>Test Results</h1>");
        }
     
        public static void addFooter(StringBuilder doc) {
            doc.append("</body></html>");
        }
     
        public static void openTable(StringBuilder doc) {
            doc.append("<table border=\"1\"");
            doc.append("<tr>");
            doc.append("<th>Name</th>");
            doc.append("<th>Score</th>");
            doc.append("<th>Grade</th>");
            doc.append("</tr>");
        }
     
        public static void closeTable(StringBuilder doc) {
            doc.append("</table>");
        }
        
        public static void addRow(StringBuilder doc, String name, String score, Grade grade){
            doc.append("<tr>");
            doc.append("<td>"+ name +"</td>");
            doc.append("<td>"+ score +"</td>");
            doc.append("<td>"+ grade.value() +"</td>");
            doc.append("</tr>");
        }
     
        public static void error(StringBuilder doc, String name, String msg, Throwable t){
            doc.append("<tr>");
            doc.append("<td>"+ name +"</td>");
            doc.append("<td colspan=2>"+ msg + " " + t +"</td>");
            doc.append("</tr>");
        }
    }
    

1. In the GradeApp application, in the Application Navigator expand Application Resources.
2. Expand Descriptors and expand META-INF and double-click to open weblogic-application.xml.
3. Add the oracle.rules library reference to the weblogic-application.xml file. Add the following lines, as shown in Figure 9-21.

   <library-ref>
       <library-name>oracle.rules</library-name>
   </library-ref>
   

   Figure 9-21 Adding Oracle Rules Library Reference to WebLogic Descriptor

   
   Description of "Figure 9-21 Adding Oracle Rules Library Reference to WebLogic Descriptor"
4. Save the weblogic-application.xml file.

1. In the Application Navigator, select the GradeApp application.
2. Right-click the GradeApp application and in the context menu select Application Properties....

   This displays the Application Properties dialog.

3. In the Application Properties navigator select the Deployment item, as shown in Figure 9-22.

   Figure 9-22 Application Properties - Deployment

   
   Description of "Figure 9-22 Application Properties - Deployment"
4. In the Application Properties dialog, click New....

   This displays the Create Deployment Profile dialog.

5. Configure this dialog as follows, as shown in Figure 9-23:

   • Archive Type: MAR File

   • Name: metadata1

   Figure 9-23 Create Deployment Profile Dialog for MAR File

   
   Description of "Figure 9-23 Create Deployment Profile Dialog for MAR File"

   Click OK.

   This displays the Edit MAR Deployment Properties dialog as shown in Figure 9-24.

   Figure 9-24 Edit MAR Deployment Profile Properties - MAR Options

   
   Description of "Figure 9-24 Edit MAR Deployment Profile Properties - MAR Options"
6. Expand the Metadata File Groups item and select the User Metadata item and click Add.

   This displays the Add Contributor dialog.

7. In the Add Contributor dialog, click the Browse button and navigate to the directory for the project that contains the GradingRules.rules dictionary file.

   In this example, navigate to C:\JDeveloper\mywork\GradeApp\Grades and click Select.

8. In the Add Contributor dialog, click OK to close the dialog. This displays the Edit MAR Deployment Properties dialog as shown in Figure 9-25

   Figure 9-25 Edit MAR Deployment Profile Properties - User Metadata

   
   Description of "Figure 9-25 Edit MAR Deployment Profile Properties - User Metadata"
9. In the Edit MAR Deployment Profile Properties dialog, expand the Metadata File Groups and expand the User Metadata item and select Directories.

   This displays the Directories page as shown in Figure 9-26.

   Figure 9-26 Edit MAR Deployment Profile Properties - Directories

   
   Description of "Figure 9-26 Edit MAR Deployment Profile Properties - Directories"
10. Select the oracle directory check box. This selects the GradingRules.rules dictionary to be included in the MAR.

    Click OK.

    JDeveloper creates an application deployment profile named metadata1 (MAR File) as shown in Figure 9-27.

    Figure 9-27 Application Properties - Deployment - MAR

    
    Description of "Figure 9-27 Application Properties - Deployment - MAR"

    Click OK in the Application Properties dialog.

1. In the Application Navigator, select the GradeApp application.
2. Right-click and in the context menu select Application Properties....
3. In the Application Properties dialog, select Deployment and click New.... This displays the Create Deployment Profile dialog.
4. Configure this dialog as follows, as shown in Figure 9-28.

   • Archive Type: EAR

   • Name: grades

   Figure 9-28 Create Deployment Profile Dialog for EAR File

   
   Description of "Figure 9-28 Create Deployment Profile Dialog for EAR File"
5. Click OK. This displays the Edit EAR Deployment Profile Properties dialog.
6. In the Edit Ear Deployment Profile Properties dialog, in the navigator select Application Assembly as shown in Figure 9-29.

   Figure 9-29 Edit EAR Deployment Profile Properties - Application Assembly

   
   Description of "Figure 9-29 Edit EAR Deployment Profile Properties - Application Assembly"
7. Configure this dialog as follows:

   • Select the metadata1 check box.

   • Expand the Grades.jpr item and select the grades check box.

8. In the Edit EAR Deployment Profile Properties dialog, click OK.

   JDeveloper creates an application deployment profile named grades(EAR File) as shown in Figure 9-30.

   Figure 9-30 Application Properties - Deployment - EAR

   
   Description of "Figure 9-30 Application Properties - Deployment - EAR"
9. Click OK to close the Application Properties dialog.
10. Select Save All from the File main menu to save your work.

1. In the Application Navigator, select the GradeApp application.
2. Right-click the GradeApp application and in the context menu select Deploy > grades > to > and select either an existing connection or New Connection... to create a connection for the deployment. This starts the deployment to the specified Oracle WebLogic Server.
3. As the deployment proceeds, Oracle JDeveloper shows the Deployment Configuration dialog.
4. In the Deployment Configuration dialog enter the following values, as shown in Figure 9-28:

   • In the Repository Name field, from the list, select: mds-soa

   • In the Partition Name field, enter grades

   Figure 9-31 Deployment Configuration Dialog for MDS with Repository and Partition

   
   Description of "Figure 9-31 Deployment Configuration Dialog for MDS with Repository and Partition"
5. In the Deployment Configuration dialog, click Deploy.

1. Point a web browser at,

   http://yourServerName:port/grades/

   This displays the test servlet as shown in Figure 9-32.

   Figure 9-32 Grades Sample Application Servlet

   
   Description of "Figure 9-32 Grades Sample Application Servlet"
2. Enter a name and test score and click Submit. This returns results as shown in Figure 9-33.

The first time you run the servlet there may be a delay before any results are returned. The first time the servlet is invoked, during servlet initialization the runtime loads the dictionary and creates a rule session pool. Subsequent invocations do not perform these steps and should run much faster.

Figure 9-33 Grades Sample Application Servlet with Results

Description of "Figure 9-33 Grades Sample Application Servlet with Results"