errors.do is an action mapping.
But your question made me take a second look at something. It appears that
the exception was getting caught and turned into an ActionError in a base
class and therefore never thrown outside the servlet, which of course
prevents it from using the global-exception. If
Configuration of global exceptions looks very simple. So I cannot understand
why the configuration of my global-exception refuses to pick up any
exceptions. If an error occurs I just get the blank white page. Here is my
global-exception configuration section.
Then I have a global-forward
I cannot get the configuration of my global-exception to pick up any errors.
If an error occurs I just get the blank white page. Here is my
global-exception configuration section.
Then I have a global-forward that looks like this
I tried specifying /errors.do as the path for the global
Struts 1.1, using Tomcat
I am trying to associate a Controller with a Struts tile. This way I can
call my business objects within the Controller to populate it appropriately
and it will be tied to the tile. So far everything has been working fine
however I run into a slight problem. It appears th
empty action.
the action just needs to return this.
return (mapping.findForward("success"));
and you'll be there.
On 12 May 2004, at 22:58, Keith Bottner wrote:
> I am trying to forward directly to a tiles definition from the
> with
>
> # struts-config.xml
I am trying to forward directly to a tiles definition from the
with
# struts-config.xml
BLAH URL
However when the JSP is generated it actually generates
BLAH URL
Any ideas on why global-forwards to tile definitions do not work?
Thanks in advance,
Keith
---
6 matches
Mail list logo
