Graphic web design - Working with test client applications Choosing the type
Working with test client applications Choosing the type of test client With three different types of test clients to choose from, it may be difficult to decide which type is right for you. The following discussion of the merits of each type of test client may help you decide. The Application type of EJB test client is the easiest to set up. It works like an application and connects to the server. Validating the test results must be done manually, however, because it does not make use of the JUnit testing framework. Use of the JUnit type of test client requires knowledge of the JUnit framework. This type of test client is highly automated and can be run as part of a test suite. Use of the JUnit framework allows automatic checking of results and good reporting capabilities. It is not as powerful as the Cactus type, because it runs the test as a client. The Cactus type of test client is the most comprehensive among the three different types. It requires Cactus and the JUnit framework, which makes setup more complex than for the other types. Cactus test cases run on the server, so they can access server-side resources. This is the only type of test client that can test an EJB 2.0 bean with a local interface. Working with test client applications This section explains how to use the EJB Test Client wizard to create a simple test client application and how to use the resulting application to test your enterprise bean. Creating a test client application JBuilder can help you create a test client application that makes calls to your new bean. To create a test client application, 1 Open the project that contains the EJB module for your enterprise bean. 2 Choose File|New, select Enterprise|EJB in the tree to display the EJB page, and double-click the EJB Test Client icon to display the EJB Test Client wizard: 92 Developing Applications with Enterprise JavaBeans
Check our reliable web hosting section. Most often, a reliable protocol is also connection-oriented. However, this is not always so. For example, TCP/IP is a connection-oriented protocol, with the virtual circuit ID consisting of source and destination IP addresses and port numbers. However, there are also unreliable protocols that are connection-oriented as well. These include ATM and Frame Relay, on which 90% or more of all Internet traffic is passed.