Note that there are some explanatory texts on larger screens.

plurals
  1. PODeploying my GWT Application on Tomcat Server
    text
    copied!<p>I want to setup a GWT application (Version 2.0.0) with many dependencys in my local Tomcat Server. I started to write a maven2 build script for deploying and packaging of the application.</p> <p>I wrote a maven2 script which works really fine in my eyes, but I get an error when trying to deploy the out coming war on my tomcat.</p> <p><code>2011-04-21 18:14:13,951 ERROR org.apache.catalina.startup.ContextConfig - Parse error in application web.xml file at jndi:/localhost/quickfinder.ui-1.0-SNAPSHOT/WEB-INF/web.xml org.xml.sax.SAXParseException: The markup declarations contained or pointed to by the document type declaration must be well-formed. </code></p> <p>The web.xml is look like the following: <a href="http://pastebin.com/uqf35CB0" rel="nofollow">here</a> and my maven2 script looks like this: <a href="http://pastebin.com/pe5HRiXf" rel="nofollow">here</a></p> <p>After compiling and linking and the other stuff my "deploy" directory (named war) looks like:</p> <p><code> |-AnswerPanel.css<br /> |-common.css<br /> |-DomainListPanel.css<br /> |-glossary.css<br /> |-glossary.html<br /> |-images<br /> |-META-INF<br /> |-MulitpleChoiceEditPanel.css<br /> |-MultipleChoiceDisclosurePanel.css<br /> |-NaviPanel.css<br /> |-QuestionnairePanel.css<br /> |-quickfinder<br /> |-Quickfinder.css<br /> |-Quickfinder.html<br /> |-quickfinderportlet<br /> |-QuickfinderPortlet.html<br /> |-styles-css2.css<br /> |-styles-css3.css<br /> |-WEB-INF<br /> |--lib </code> Under lib in the WEB-INF directory, all needed library's are available. The Project has got some RPC calls and so on.</p> <p>With <code>mvn compile war:war</code> a .war file and a folder named #artifactId#-SNAPSHOT-1.00 are created under /target.</p> <p>I don't know how to handle with this error form tomcat, or is there a logical mistake in the pom.xml.</p> <p>BR, mybecks</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload