Rich Garabedian said: > Complete stack trace displayed in web page. Web.xml follows after thant
yeah, i know there's a stack trace, but when it's for a MethodInvocationException, it's the "wrong" trace. it'll only trace to where the MIE was thrown, not to where the exception that triggered the MIE was thrown. ... > Web.xml: ... > <web-app> > <display-name>Struts Blank Application</display-name> > > <!-- Standard Action Servlet Configuration (with debugging) --> > <servlet> > <servlet-name>action</servlet-name> > > <servlet-class>org.apache.struts.action.ActionServlet</servlet-class> > <init-param> > <param-name>config</param-name> > <param-value>/WEB-INF/struts-config.xml</param-value> > </init-param> ... > <load-on-startup>2</load-on-startup> > </servlet> > > > <!-- Define Velocity template compiler --> > <servlet> > <servlet-name>velocity</servlet-name> > <servlet-class> > org.apache.velocity.tools.view.servlet.VelocityViewServlet > </servlet-class> > > <init-param> > <param-name>org.apache.velocity.toolbox</param-name> > <param-value>/WEB-INF/toolbox.xml</param-value> > </init-param> > > <init-param> > <param-name>org.apache.velocity.properties</param-name> > <param-value>/WEB-INF/velocity.properties</param-value> > </init-param> > > <load-on-startup>10</load-on-startup> > </servlet> > > <!-- Map *.vm files to Velocity --> > <servlet-mapping> > <servlet-name>velocity</servlet-name> > <url-pattern>*.vm</url-pattern> > </servlet-mapping> > > <!-- Standard Action Servlet Mapping --> > <servlet-mapping> > <servlet-name>action</servlet-name> > <url-pattern>*.do</url-pattern> > </servlet-mapping> > > <!-- The Usual Welcome File List --> > <welcome-file-list> > <welcome-file>templates/welcome.vm</welcome-file> ... > </welcome-file-list> > > </web-app> ... yeah, that looks alright to me. so i'm guessing that Ted's guess is right. if you want to interact with Struts stuff on the welcome page, you should first take a trip through the ActionServlet with a welcome action in order to get the ActionServlet all fired up. i don't think there's much we can do when it comes to VelocityTools except try to give a more meaningful error message. Nathan Bubna [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
