Deploying the xmlwebgui web application
Prev Chapter 1. Installation Next

Deploying the xmlwebgui web application

In most servlet engines, this is just a matter of copying the xmlwebgui.war file in a specific directory and the engine will take care of installing it when restarted. In some servlet engines you will have to change the xml parser used.

Deploying on Tomcat 3.2+.  Tomcat currently uses a different version of the XML parser than xmlwebgui. To get xmlwebgui to work, you need to perform the following steps:

  1. Stop Tomcat Go to the tomcat/bin directory, and run the shutdown script.
  2. Delete tomcat/lib/jaxp.jar Tomcat's jaxp.jar is 'sealed', and since xerces contains its own implementation of the JAXP standard extension, Java will fail to load xerces and report a 'Package Sealing Violation' if both are in the classpath.
  3. Rename tomcat/lib/parser.jar to tomcat/lib/zparser.jar Tomcat's parser.jar contains older versions of some the same XML APIS that Xerces uses, and these will prevent Xerces from functioning properly if they appear before Xerces in the classpath. Since Tomcat's startup scripts automatically load all the jar files in tomcat/lib in name order, changing the name of the file causes it to be loaded last in the classpath.
  4. Copy wmlwebgui.war to xmlwebgui.zip and unpack it to a directory called xmlwebgui
  5. Copy the xmlwebgui/lib/xerces.jar and xmlwebgui/lib/xalan.jar files to tomcat/lib xmlwebgui will now be able to see and use the correct XML libraries.
  6. Copy xmlwebgui.war into tomcat/webapps
  7. Start Tomcat Go to the tomcat/bin directory, and run the startup script.
  8. Start using xmlwebgui Access the URI http://localhost:8080/xmlwebgui/ with a DOM-conformant browser[1]. Tomcat will unpack the xmlwebgui.war.

  9. Edit xmlwebgui/WEB-INF/web.xml In this file you will find a parameter that must be customized to make xmlwebgui run. Find the following part of the file 

                      
<context-param>
		<param-name>rootDir</param-name>
		<!-- Enter the base path for templates and results here -->
		<param-value>C:/java/tomcat401/webapps/xmlwebgui/</param-value>
</context-param>
<context-param>
		<param-name>applicationDir</param-name>
		<!-- Enter the base path for the application here -->
		<param-value>C:/java/tomcat401/webapps/xmlwebgui/</param-value>
</context-param>
    Edit the paths that it points to your xmlwebgui installation directory.

Deploying on Tomcat 4.x.  Tomcat 4.x is a really straight-forward installation

  1. Stop Tomcat Go to the tomcat/bin directory, and run the shutdown script.
  2. Copy xmlwebgui.war into tomcat/webapps
  3. Start Tomcat Go to the tomcat/bin directory, and run the startup script.
  4. Start using xmlwebgui Access the URI http://localhost:8080/xmlwebgui/ with a DOM-conform browser[1]. Tomcat will unpack the xmlwebgui.war.

  5. Edit xmlwebgui/WEB-INF/web.xml In this file you will find a parameter that must be customized to make xmlwebgui run. Find the following part of the file 

                      
<context-param>
		<param-name>rootDir</param-name>
		<!-- Enter the base path for templates and results here -->
		<param-value>C:/java/tomcat401/webapps/xmlwebgui/</param-value>
</context-param>
<context-param>
		<param-name>applicationDir</param-name>
		<!-- Enter the base path for the application here -->
		<param-value>C:/java/tomcat401/webapps/xmlwebgui/</param-value>
</context-param>
    Edit the path that it points to your xmlwebgui installation directory.

Deploying xmlwebgui on another servlet engine.  Please refer to your servlet engine's documentation. FIXME

Prev Up Next
Getting xmlwebgui Home Chapter 2. Running the examples