wst common test plan: wtp project explorer. |
Exporting modules | ||||||
Modules that are created in WTP may be exported in various ways. The following instructions focus on exporting modules as deployable artifacts. First, you must have previously imported or created a module. (For instance, a Dynamic Web Module). | ||||||
Exporting a web modules | ||||||
| ||||||
Initially, the export wizard should have the project that contains the Web Module you selected. Enter a destination for the export (e.g. C:\temp\mywar.war). When you are done, click Finish. The wizard will handle the details of constructing the Web Module per the J2EE specification. Optionally, you can choose to export the source files. Exporting source files can be useful when you intend to use the war for collaboration or like to keep a record of what is contained in the *.war file. You may verify the contents of the *.war file using your favorite Zip File client. | ||||||
Each of the types of modules has their own specific Export wizard. Try exporting another type of module. For instance, you may export the *.ear file that contains the Web Module you just exported by selecting the EAR Module, right-click, and then select "Export > EAR File". The wizard is largely similar to the Web Module Export wizard. It will construct a *.ear file that contains all of the other modules. | ||||||
The artifacts produced from the export wizards are ready to deploy onto your favorite Web Container or J2EE Application Server. Some containers like Tomcat require only the *.war file to deploy, while other full-service J2EE Application Servers like Websphere Application Server require a *.ear file. | ||||||
Return to overview. |