JWAD > Installation
JWAD consists of two files...
  • jwad-server.war
    • This WAR simply serves the images, styles, and scripts necessary to run the DTHML console. The reason it is deployed as a separate web-app is to simplify installation. Were it not so, JWAD-specific artifacts would be scattered throughout your domain's web application. The intent was to be non-intrusive.
  • jwad-client.jar
    • This JAR contains all the Java code necessary to access the various objects in their respective scopes. It simply gets the objects, categorizes, and then prints them to the output stream.
Once downloaded and extracted...
  1. Copy the "jwad-client.jar" to your web-app's "WEB-INF/lib" folder.
  2. If necessary...
    • Modify your ANT build script.
  3. Add the following context parameters to your "web.xml" deployment descriptor. Be sure to replace the [domain] and [port] placeholders with your own corresponding values.
    • <context-param>
	<param-name>jwadEnabled</param-name>
	<param-value>true</param-value>
</context-param>
<context-param>
	<param-name>jwadServer</param-name>
	<param-value>http://www.[domain].com:[port]</param-value>
</context-param>
    Note: You may optionally omit the "jwadServer" context parameter altogether if the "jwad-server.war" is deployed on the same server as your domain web application (the one with "jwad-client.jar").
  4. Add the following taglib declaration and custom tag include to your JSP template (or pages).
    • <%@ taglib uri="http://www.solarbox.com/tags/jwad" prefix="jwad" %>
<jwad:debugger />
    Note: To control the number or order of modules (scopes) displayed in the JWAD console, use the optional "modules" attribute of the <jwad:debugger /> custom tag. Acceptable (comma-seperated) values include the following...
    • Page
    • Request
    • Session
    • Application
  5. Deploy the "jwad-server.war" to your web container.
  6. Deploy your domain's web-app.
That's it! JWAD is ready to use.
Copyright ©2010, Solarbox - All Rights Reserved.