| <?xml version="1.0" encoding="UTF-8"?> |
| <?xml-stylesheet type="text/xsl" href="../../../../wtp.xsl"?> |
| <html> |
| <head> |
| <meta name="root" content="../../../../.." /> |
| <title>test plan: Java Jar Dependencies</title> |
| </head> |
| |
| <body> |
| <h1>jst j2ee</h1> |
| |
| <h2>Introduction</h2> |
| <p>This test plan walks you through the scenario of how to set up j2ee jar dependencies between modules in an Enterprise Application module (EAR) that is used for application development and deployment. The jar dependencies can only be set within the boundaries of an Enterprise Application.<br/> |
| <br/> |
| Web modules are an exception where utility jar dependencies can be set on standalone web modules too which is explained in Web Utility Jars test plan. |
| </p> |
| |
| <h2>Prerequites</h2> |
| <p>This test plan scenario works on WTP 0.7 M5 or later milestone releases.<br/> |
| </p> |
| |
| <h2>Steps</h2> |
| <p> |
| <ol> |
| The Java Jar Dependencies properties page is used to setup jar dependencies between modules in an EAR. To launch this properties page right click on any j2ee module project (application client, web, ejb, connector) and select <b>Properties</b>-> <b>J2EE Module Dependencies</b>--> <b>J2EE Modules</b><br/> |
| <br/> |
| <br/> |
| <li> Create an EAR with all the default modules (Application Client, Web, EJB, Connector) by going through the second page in the EAR creation wizard.<br/> |
| <br/> |
| </li> |
| <li> Right click on the Web module created and select <b>Properties</b>-> <b>J2EE Module Dependencies</b>--> <b>J2EE Modules</b><br/> |
| <br/> |
| <table |
| cellspacing="10" |
| cellpadding="10"> |
| <tr> |
| <td> |
| <img src="images/jardependencies.jpg" /> |
| </td> |
| </tr> |
| </table> |
| </li> |
| |
| <li> The EJB and Connector modules show up as the available modules that the web module can have dependency on in the EAR. Select the ejb module and click <b>OK</b> or <b>Apply</b><br/> |
| <br/> |
| <b>Result:</b> The following changes occur on setting the jar dependency of the ejb module on the web module. <br/> |
| |
| The MANIFEST.MF file gets an entry for each selected module. <br/> |
| The .classpath file of the module gets updated with an entry for the selected modules. <br/> |
| The .project files gets updated with the project dependency. |
| |
| <br/> |
| </li> |
| <li> The <b>Manifest Class-Path</b> non editable text area show the list of select modules that are added on to the Manifest. <br/> |
| <br/> |
| </li> |
| |
| <li> The <b>Up</b> and <b>Down</b> buttons are used to move the order or the selected modules that are added on to the Web Module in this case. |
| <br/> |
| </li> |
| <br/> |
| <li>The 3 radio buttons <b>Use EJB JARS, UseEJB Client JARs and Allow both</b> are used for filtration of having only client jars or EJB Jars or both as the available modules for dependency.<br/> |
| <br/> |
| </li> |
| <li> |
| Right click on Java project to invoke this property page, verify that no errors are thrown.<br/> |
| <br/> |
| </li> |
| </ol> |
| </p> |
| |
| |
| </body> |
| </html> |
