I was using the standard JBoss 3.2.1/Jetty (4.2?) bundle and decided to
try 3.2.3 bundled with Tomcat (4.1.29). I deployed the same exact .ear
to both, trying one and then the other. They both startup fine and
deploy the .ear.with no exceptions, but when attempting to display a
page via an Action, 404 page is shown saying "The requested resource
(/home.action) is not available." The console log actually shows the
action executing and the debugger shows the action execute() method
returning SUCCESS, so it look like what is actually not being found is
the JSP. My JSPs are sitting in /WEB-INF/jsp. So why would the same
ear work under Jetty, and not Tomcat?
Fred.
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
