9.7 Testing the Web Application

Procedures for testing the web application vary depending on whether or not you elect to use ADF data binding in the application. If you do not use ADF data binding, your testing and debugging scenarios can follow any generic web testing and debugging procedures.

To specifically test and debug a web service invocation, you can use the client class generated when you created the proxy to the web service. Example 9-18 shows the code you might use to test the web service by finding a customer whose ID is 1.

Example 9-18 Testing the Web Service Using the Client Class

public static void main(String[] args) {
  try {
       model.proxy.CustomerServiceClient myPort = new
                                       model.proxy.CustomerServiceClient();
       System.out.println("calling " + myPort.getEndpoint());
      // Add your own code here
      myPort.findCustomerById("1");
     } catch (Exception ex) {
       ex.printStackTrace();
  }
}

You can also test the web service using JDeveloper's HTTP Analyzer. For more information, see Section 5.4, "Debugging, Testing and Analyzing Web Services in JDeveloper".

Most failures in the web application's interaction with Oracle ADF result from simple and easy-to-fix errors in the declarative information that the application defines or in the EL expressions that access the runtime objects of the page's Oracle ADF binding container. Refer to Oracle Application Development Framework Developer's Guide for more information regarding troubleshooting and debugging ADF applications.