Figure 6.9 127 Project Development Figure 6.10
Do you have a godaddy domain name? If you do, you have found the right web hosting provider for you.Our Godaddy Web Hosting packages are the best match to well known, affordable godaddy domain names.
Try It Out: Javadoc Options In the next step you can determine the content and the layout of the single Javadoc pages. The following options exist: . Generate Use Page. This option allows you to generate a cross-reference for each class and each package. . Generate Hierarchy Tree. When you check this option, a page is generated that displays the hierarchy of packages, classes, and interfaces. . Generate Navigator Bar. This option generates a navigation bar at the top and at the bottom of each page. . Generate Index. This option generates one or several index pages. . Separate Index per Letter. Check this option to generate a separate index page for each letter in the alphabet. . @author, @version, @deprecated. When these options are set, the corresponding key words in the Javadoc comments are evaluated and their information is included in the generated pages. . Deprecated List. This option allows a separate page to be generated, listing all elements marked as deprecated. In addition, you can create links to other Javadoc documentations. Try It Out: Command-Line Options On the next wizard page (Figure 6.9), you can specify additional command-line options for javadoc .exe, if necessary. In addition, you can specify a file containing additional text for the Javadoc Overview page. The JRE 1.4 Source Compatibility option must be checked if your source code contains the Java assert keyword. Without this option set, Java 1.4 programs that contain this instruction would cause errors during the Javadoc generation. Checking this option is equivalent to specifying the command-line option -source 1.4. You can also optionally create an Ant script for Javadoc generation (Figure 6.10). I will discuss Ant in more detail in Chapter 13. After you press Finish, the Javadoc generation is started as a batch job. The output of the batch job appears on the Eclipse Java console. 126 Chapter 6
Our window web hosting plans are bursting with features and FREE tools, at the very small rate. Sign up today window web hosting.
Documentation In the Java Information Windows section in Chapter 2 you saw how Javadoc comments can be conveniently added to source code. In this section I will discuss how these comments can be exported as an HTML Javadoc documentation. To generate the Javadoc documentation for the completed DukeSpeaks project, select the project and invoke the Export context function. On the first page of the Export Wizard, select Javadoc from the list and press the Next button. On the following page, you can specify in detail what should be exported to Javadoc (Figure 6.8). But first make sure that the Javadoc Command entry points to a valid Javadoc processor such as …j2sdk1.4.2binjavadoc.exe and that the Destination entry specifies a destination folder for the Javadoc pages. You can preset a default value by applying the Properties > Javadoc Location context function to the project. You can also specify for which packages and for which methods Javadoc is to be generated. In addition, you have the option of using a custom doclet instead of Sun Microsystems reference implementation. 125 Project Development Figure 6.8
If you need complete web hosting solution you come to right place,try mac web hosting services.
Here, I have created a test suite solely for demonstration purposes. If you want to run only a single TestCase class, creating a test suite is not really required. Running a Test Suite Now you can execute all tests. Invoke the Run > Run as > JUnit Test function. Eclipse opens the JUnit view (in front of the Package Explorer) and runs the test suite (Figure 6.7). 124 Chapter 6 Figure 6.7 In the upper part of the JUnit View all errors are collected (to a maximum of one error per single test case). The other stacked window in the upper area shows the hierarchy of test suites and single test cases. In the lower part of the view, JUnit shows the execution stack for the currently selected error. Here, to force an error, I specified a panel width (650) in the test case that was different from the panel width specified in the application.
We will hook you up with a JSP web hosting at the great rate, check our jsp web hosting, and join us today!!!
method before executing the run() method. Similarly, the tearDown() method is called after all tests are executed. This method can be used to dispose of resources. When you have created several TestCase classes, it makes sense to combine these classes in a test suite. The JUnit Wizard will help you with this task, too. You only have to invoke the File > New > Other > Java > JUnit > Test Suite function. In the wizard s selection list checkmark all TestCase classes that you want to add to the test suite (in this example the only test case is the PlayerTest class); see Figure 6.6. At this point it is even possible to add other test suites to the new test suite, i.e., you may nest test suites. In the Test Suite field change the proposed name AllTests according to your requirements. 123 Project Development Figure 6.6 After you press the Finish button, the wizard will generate the resulting TestSuite class: import junit.framework.Test; import junit.framework.TestSuite; public class AllTests { public static Test suite() { TestSuite suite = new TestSuite(”Test for tests”); //$JUnit-BEGIN$ suite.addTest(new TestSuite(PlayerTest.class)); //$JUnit-END$ return suite; } }
Get account with us and you will get completely access to our free web templates database with over 10.000 templates in it to build your website.Don’t wait, go and check free web templates.
Creating a Test Suite All generated test methods start with the string test. JUnit recognizes such method names and executes them when running a test. Since the wizard has already generated the method stubs, you need only add the code inside the method body. If you need to initialize variables or other resources, you do this in the setUp() method. See Listing 6.1. import junit.framework.TestCase; import com.bdaum.dukeSpeaks.Player; public class PlayerTest extends TestCase { Player player; /** * Constructor for TestCase1. * @param arg0 */ public PlayerTest(String arg0) { super(arg0); } /** * Initialize the player */ protected void setUp() throws Exception { super.setUp(); player = new Player(”Animated FreeTTS Player”); } final public void testGetWidth() { assertTrue(”width != 600: “+player.getWidth(), player.getWidth() == 600); } final public void testGetHeight() { assertTrue(”height != 500: “+player.getHeight(), player.getHeight() == 500); } /** * Dispose of everything */ protected void tearDown() throws Exception { super.tearDown(); player = null; } } Listing 6.1 Here, two tests (testWidth() and testHeight()) are implemented. In these tests the JUnit assertTrue() method is used to test a condition and throw an exception if the condition is not met. Both methods use the player variable that was initialized in the setUp() method. JUnit calls this 122 Chapter 6
We strive to offer the highest quality service while maintaining a cheap and discount price structure. For your company, ecommerce, or personal web hosting needs, we offer the best solution.Trust us and please check quality web hosting services.
Figure 6.4 121 Project Development Figure 6.5
We are the cheapest Catholic web hosting provider, check Catholic Web Hosting services and make sure of alone.
JUnit JUnit is an Open Source tool that allows you to create and execute test suites quickly and systematically. The people behind JUnit are Kent Beck and Erich Gamma. Since Erich Gamma is also significantly involved in the development of Eclipse, it is no surprise that JUnit is contained in the Eclipse SDK distribution. Detailed information is available at www.junit.org or in Professional Java Tools for Extreme Programming by Richard Hightower, et al. Test tools such as JUnit are used to test program modules repeatedly, especially after changes have been applied to a module. Using such automated test tools allows you to test frequently and after each small incremental development step, following the XP motto: Code a little, test a little. Of course, the quality of the test results stands or falls with the quality of the test suite. A good test suite should cover the whole functional range of a program module. This is, however, easier said than done! Setting Up JUnit To be able to work with JUnit, the JUnit JAR file is required in the build path of your project. You could manually add junit.jar as an external JAR file to DukeSpeaks project, as described in the Project Properties section in Chapter 4. You can find junit.jar under eclipsepluginsorg .junit_3.8.1. However, this is not really required, since Eclipse will do this for you when you create your first test case. In the DukeSpeaks project you can now create a test case class (a subclass of the JUnit TestCase class), which you can call PlayerTest. You can create such a class manually, or you can use the JUnit Wizard (Figure 6.4) in which case you proceed as follows: 1. Invoke the wizard via the File > New > Other > Java > JUnit > Test Case function. 2. In the first page of the wizard, press the Browse button at the Class to Test field and select the class that you want to test (Player). 3. To name the test, enter PlayerTest in the Name field. 4. In the Package field select a target package (within your project) for the new TestCase class. 5. Additional options allow you to generate a main() method, a setUp() method, a tearDown() method, and a constructor for the new test case. On the next page of the wizard select which of the test class test methods are to be generated (Figure 6.5). Here I have selected only two methods. Normally you would first select all methods and then explicitly deselect all the methods that you don t want to test. Optionally, you can decorate all generated methods with the modifier final. TODO comments can be generated into the method stubs. 120 Chapter 6
We are the the largest streaming host company, and we provide professional audio & video web hosting streaming using Real Networks, QuickTime, Flash and Windows Media.We strongly recommend you to visit and check web hosting streaming services.
Note, that each test run creates a new console instance. In the Console View you can select which console to display by clicking the arrow button. Remote Debugging Remote debugging is used for applications that run on a remote JVM, especially for an application that runs outside the Eclipse platform. Typical targets for remote debugging are servlets that have neither a GUI nor a console. To make a Java application accessible to an external debugger, you must specify additional commandline parameters when starting the application s JVM. In the following example assuming that this application has already been installed outside Eclipse I demonstrate how DukeSpeaks can be made accessible to a remote debugger: java.exe -Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=y, address=8787 -classpath %LOCALCLASSPATH% com.bdaum.dukeSpeaks.Player First, the JVM is switched into debug mode. The sun.tools.debug agent is switched off, as well as the JIT and HotSpot compilers. With Xrunjdwp the reference implementation of the Java Debug Wire Protocols (JDWP) is loaded. A socket connection is selected as transport mode. The server=y parameter specifies that the application acts as a debug server, and the suspend=y parameter specifies that the application must not start autonomously but must wait for a connection with the debug client. Finally, the address=8787 parameter specifies the debug port number that can be selected from the host computer s free ports. Now, start the application and execute the command. Nothing happens. The application waits for the debug client. Now it s time to create a remote debug configuration in Eclipse. To do so, invoke the Run > Debug function. In the selection list at the left-hand side of the dialog, select Remote Java Application and press the New button. Then enter a name for the new configuration (for example, DukeSpeaksRemote) and select the project (DukeSpeaks). This specification is actually not used to tell the Eclipse debugger the location of the binary files but to inform it about the location of the source files. The Connection Type field remains unchanged: Standard (Socket Attach). Since the remote application runs on the same host computer, you must enter the localhost value under Host. For Port, specify exactly the same value that was used above in the java command. So enter 8787. Finally, mark the Allow Termination of Remote VM checkbox. This allows you to terminate the application via remote control from the Eclipse debugger. Now the configuration is properly set up. You can start the debugging process by clicking the Debug button. From now on, everything works just as with local debugging. You can set breakpoints, look at variables, and even modify the values of variables. The only thing that does not work with remote debugging is, of course, HotSwapping. 119 Project Development
We know it is important decision to make, effects your wallet, and the quality of your web site, so relax and visit shared web hosting.
Figure 6.3 If you have trapped an exception with such a breakpoint, program execution is interrupted when the exception occurs. In the Debug window you now can select a method within the stack trace shown under the current thread. The Variables View shows you the variables of the method s execution environment, so that in most cases you can easily determine the reason for the exception. Finally, the Skip All Breakpoints tool button in the Breakpoints window allows you to disable all breakpoints temporarily. The Java Console Although the debugger provides you with a rich arsenal of tools to find bugs in programs, you should not ignore the Java console. To find a problem, it is sometimes simpler to program a test output into a method or constructor instead of spending ages stepping through program code. You can accomplish such outputs with System.out.println() or System.err.println(). By using the Code Assistant (see the Java Information Windows section Chapter 2), you can simply enter sysout or syserr to create such an instruction. In the case of a program crash, the console is a valuable source of information, too, since it displays the execution stack. Eclipse here offers additional help: double-clicking a stack entry opens the corresponding compilation unit and positions the editor window to the specified line! 118 Chapter 6
Our company is website hosting provider which offers web hosting services for php, java, mysql, frontpage, dreamweaver and domain name registration. Check more about us on website hosting provider part.