This week's book giveaway is in the OCAJP forum. We're giving away four copies of OCA Java SE 8 Programmer I Study Guide 1Z0-808 and have Jeanne Boyarsky & Scott Selikoff on-line! See this thread for details.
I'm getting a filterStart error when I try to start Tomcat and deploy my 1st struts application.Apparently the problem is in configuration of my web-app....Here is a tree of my DBTest web- app:
│ │ └───DBTest
The lowest DBTest folder in the tree contains test4.jsp...A jsp I am trying to hit using an empty action..
This is my package declaration in struts.xml(struts.xml is in \DBTest\WEB-INF\classes):
And (most) of my web.xml(web.xml is in \DBTest\WEB-INF\):
I just want to enter http://localhost:8080/DBTest/tester.action and use the empty action to hit test4.jsp.This would be like hitting the test4.jsp directly?I also tried making an action class but it can't find package org.apache.action.Action...I have all the necessary JARs in the DBTest web-app's lib folder:
Maybe it's my classpath...I have set my classpath to apache\common\lib..Which also contains the above jars(and the others)...
Is this it:
[SEVERE]:Context [\DBTest] startup failed due to previous errors
I took that output directly from the Tomcat console(not the logs) if that makes a difference.
And if I try to compile the action class I get the following:
tester.java:2: package org.apache.struts.action does not exist
tester.java:3: cannot find symbol
symbol: class Action
public class tester implements Action
My struts is not working at all...The Struts2InAction.war that I deployed doesn't even work...But I thought this application contains all the dependancies it needs...so how could I have stopped it from working(I redownloaded the sample application to make sure that I hadn't edited any of the files)I no longer get struts errors when I try to run the application either.....just the regular tomcat errors...
I find it unlikely it's a Tomcat installation issue; that's a matter of unzipping the distro. One doesn't really "install" Struts, but it could be an issue with how you tried to deploy the application (normally just putting the war file into the "webapps" directory is sufficient--by default Tomcat will deploy war files found there).