WebSphere Studio Application Developer part 68 provides integrated development tools for all e-business development roles, including Web developers, Java developers, business analysts, architects, and enterprise programmers. The customizable, targeted, role-based approach of WebSphere Studio Application Developer will be characteristic of all new products built on the WebSphere Studio Workbench. It is well integrated with WebSphere Application Server and provides built-in server test environments that can be used for testing and profiling Web applications | Forced build To generate a complete build select the clean target as the first target and the di st target as the second target to run. You have to de-select dist select clean and then select dist again to get the execution order right Figure 19-9 . Figure 19-9 Launching Ant to generate complete build Classpath problem The classpath specified in the Java build path for the project is unfortunately not available to the Ant process. If you are building a project that references another project the classpath for the javac compiler must be set up in the following way javac srcdir source destdir build includes .java classpath pathelement location . MyOtherProject pathelement location . MyThirdProject classpath javac Building J2EE applications As we have just shown building a simple Java application using Ant is quite easy. Now we will also show you how to use Ant to build your J2EE projects. EAR WAR and EJB JAR files all contain a number of deployment descriptors that control how the artifacts of the application are to be deployed onto an 644 WebSphere Studio Application Developer Version 5 Programming Guide application server. These deployment descriptors are mostly XML files and are standardized in the J2EE specification. While working in Application Developer some of the information in the deployment descriptors is stored in XML files but these files also contain information in a format convenient for interactive testing and debugging. That is part of the reason it is so quick and easy to test J2EE applications in the internal WebSphere Application Server included with Application Developer. The actual EAR being tested and its WAR EJB and client application JARs are not actually created as a standalone file. Instead a special EAR is used that simply points to the build contents of the various J2EE projects. Because these individual projects can be anywhere on the development machine absolute path references are used. When an Enterprise Application project is exported
