A note on war file deployment error with wicket

[Fei]

Just put this down as a note:

When we deploy the wicket webapp as a war file to the servlet
container, the wicket-{version}.jar file seems have to be included due
to the WicketFilter, which is used in the web.xml, comes from that jar
file.

Tomcat gives very vague error message for this problem:

SEVERE: error filterStart

Jetty gives a more descriptive error message in this case. It actually
tells which class is not found.

To deploy a war file into jetty, simply copy the war file to
JETTY_HOME/webapps, and then run "java -jar start.jar" in the same
directory.

[Nathan Britton]

Oh, sweet - good show on finding how to deploy a raw war file; that should alleviate some of the tomcat BS.  I will see if I can find out how/whether our code creates a war file with Jetty.

--
Nathan Britton

The only impossible task is to find an impossible task.

[Fei]

Some more note:

After including wicket-{version}.jar file in the WEB-INF/lib folder,
the war file can be deployed without problem. Then it comes another
problem of HTML markup not found.

To avoid that problem, we put back the html to the same place as the
classes files. The webapp runs normally but without CSS formating.

But then there is another more important problem, the embedded jetty
doesn't run correctly with the wicket-{version}.jar file added to the
WEB-INF/lib folder. Somehow it says org/slf4j/LoggerFactory class not
found. Maybe we should only copy the jar file when we are creating the
war file.