I think we've got the problem solved now. One of the developers found
that in one case the path was actually hard-coded in a JSP. Ugh! We
also had not provided a namespace for our struts package, and so
apparently it was defaulting to the package name. Just little details
that get left until the last minute.
ChadDavis wrote:
2) Is it possible to not have to have the base path defined in Struts at
all? It seems to me that this would be the ideal solution.
If you deploy the app as the root app in the servlet container, then
your struts namespaces are essentially doing this. I think the net
effect is what you are looking for. But maybe I misunderstand
something.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org
