The xml-dom4j quickstart is a simple DOM4J example that demonstrates how to use Servlet 3.0 and JSF to upload an XML file to Red Hat JBoss Enterprise Application Platform and parse it using a 3rd party XML parsing library.
It also shows how to include 3rd-party library in a deployment.
The application this project produces is designed to be run on Red Hat JBoss Enterprise Application Platform 7 or later.
All you need to build this project is Java 8.0 (Java SDK 1.8) or later and Maven 3.1.1 or later. See Configure Maven for JBoss EAP 7 to make sure you are configured correctly for testing the quickstarts.
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.
Jan 20, 2016(Sande Gilda):JBEAP 2905 Update property in xml dom4j POM file for version.dom4j to 1.6.1 and remove source warning in README file
Sep 1, 2015(Sande Gilda):JBEAP 622 Add warning about missing dom4j source to xml dom4j README
Aug 20, 2015(Sande Gilda):JBEAP 577 Replace links to shared resources for JBoss EAP 7 material
Aug 4, 2015(Sande Gilda):JBEAP 578 Update Maven version in README files
Aug 3, 2015(Sande Gilda):JBEAP 564 Clarify Maven instructions
Jul 23, 2015(Sande Gilda):Replace CONFIGURE_MAVEN link with CONFIGURE_MAVEN_JBOSS_EAP7 link
Jun 24, 2015(Sande Gilda):JDF833 Plugin commands have changed from jboss as prefix to wildfly prefix. jboss as deploy is now wildfly deploy and jboss as undeploy is now wildfly undeploy. Same replacement for port and hostname
Jun 17, 2015(Sande Gilda):Update the quickstart README files to remove instructions related to the Maven settings
Jun 2, 2015(Sande Gilda):Update quickstart files to remove JBoss EAP version and update to Java EE 7 and SDK 1.8. Replace references to WFK and Sandbox with EAP
Mar 4, 2015(Sande Gilda):Bz1198744 Update README JBDS instructions to be more clear