Thanks Craig. Everything was set up correctly, but you got me thinking
about the init method of the controller servlet. I unfortunately ASSumed
that the ActionServlet overrode the init(ServletConfig) method and that the
no-parameter init() was free for the taking. In fact, ActionServlet
overrides init(), so I just inserted a call to super.init() and wa-la!
- Mark.
> * Do you still have the <load-on-startup> element in your web.xml file
> to cause the controller servlet to be loaded when the application is
> initialized? Without this, you'd get the error you encountered if the
> very first request goes to a JSP page rather than an action.
Yes, in fact, I know the init method is running because
>
> * Do you have an <init-param> defining the correct location of the
> application resources in your controller servlet definition? Check the
> Tomcat log file messages for clues (the controller servlet will complain
> if it cannot load the application resources).
>
> Craig McClanahan
