xml-jaxp: Upload and Parse an XML File Using DOM or SAX

The xml-jaxp quickstart demonstrates how to use Servlet and JSF to upload an XML file to WildFly and validate and parse it using DOM or SAX.

What is it?

The xml-jaxp quickstart is a simple Java EE JAXP example that demonstrates how to use Servlet 3.0 and JSF to upload an XML file to WildFly Application Server and parse it using DOM or SAX, both of which are built into Java. It also shows how to use modules available in WildFly.

This quickstart provides an example XML schema and document file to use when testing this quickstart.

The XML schema is located here: QUICKSTART_HOME/src/main/resources/catalog.xsd
The XML document is located here: QUICKSTART_HOME/src/main/resources/catalog.xml

System Requirements

The application this project produces is designed to be run on WildFly Application Server 13 or later.

All you need to build this project is Java 8.0 (Java SDK 1.8) or later and Maven 3.3.1 or later. See Configure Maven to Build and Deploy the Quickstarts to make sure you are configured correctly for testing the quickstarts.

Use of WILDFLY_HOME

In the following instructions, replace WILDFLY_HOME with the actual path to your WildFly installation. The installation path is described in detail here: Use of WILDFLY_HOME and JBOSS_HOME Variables.

Start the WildFly Standalone Server

Open a terminal and navigate to the root of the WildFly directory.
Start the WildFly server with the default profile by typing the following command.
```
$ WILDFLY_HOME/bin/standalone.sh 
```
Note
For Windows, use the WILDFLY_HOME\bin\standalone.bat script.

Build and Deploy the Quickstart

Make sure you start the WildFly server as described above.
Open a terminal and navigate to the root directory of this quickstart.
Type the following command to build the artifacts.
```
$ mvn clean package wildfly:deploy
```

This deploys the xml-jaxp/target/xml-jaxp.war to the running instance of the server.

You should see a message in the server log indicating that the archive deployed successfully.

Access the Application

The application will be running at the following URL: http://localhost:8080/xml-jaxp/.

To test the quickstart, follow these steps.

Click the Browse button and navigate to the QUICKSTART_HOME/src/main/resources/catalog.xml file.
Click the Upload button. The XML file content is parsed and displayed on the page.
You should see the following output in the server console that shows the DOMXMLParser was used:
```
INFO  [stdout] (http-/127.0.0.1:8080-1) Parsing the document using the DOMXMLParser!
```

To enable the alternative SAXXMLParser parser:

Remove the comments that surround the alternate parser element in the WEB-INF/beans.xml file.
Redeploy the application using the instructions above and access the application in a browser at the following URL: http://localhost:8080/xml-jaxp/.
Click the Browse button and navigate to the QUICKSTART_HOME/src/main/resources/catalog.xml file.
Click the Upload button. The XML file content is parsed and displayed on the page.

You should now see following output in the server console:

INFO  [stdout] (http-/127.0.0.1:8080-1) Parsing the document using the SAXXMLParser!

Undeploy the Quickstart

When you are finished testing the quickstart, follow these steps to undeploy the archive.

Make sure you start the WildFly server as described above.
Open a terminal and navigate to the root directory of this quickstart.
Type this command to undeploy the archive:
```
$ mvn wildfly:undeploy
```

Run the Quickstart in Red Hat JBoss Developer Studio or Eclipse

You can also start the server and deploy the quickstarts or run the Arquillian tests in Red Hat JBoss Developer Studio or from Eclipse using JBoss tools. For general information about how to import a quickstart, add a WildFly server, and build and deploy a quickstart, see Use JBoss Developer Studio or Eclipse to Run the Quickstarts.

Debug the Application

If you want to debug the source code of any library in the project, run the following command to pull the source into your local repository. The IDE should then detect it.

$ mvn dependency:sources