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.
global-exceptions
exception
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.
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.
global-exceptions
exception key=exception.application path=errors
type=java.lang.Exception / /global-exceptions
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
I am trying to forward directly to a tiles definition from the
global-forwards with
# struts-config.xml
global-forwards
forward name=signon path=.alt.signon /
/global-forwards
My JSP page uses:
html:link forward=signonBLAH URL/html:link
However when the JSP is generated it actually
an empty action.
action path=/myaction type=com.foo.struts.EmptyAction
forward name=success path=mytiledef redirect=false /
/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
6 matches
Mail list logo