You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@shale.apache.org by "Torsten Krah (JIRA)" <ji...@apache.org> on 2006/11/06 11:37:57 UTC
[jira] Commented: (SHALE-277) Shale is eating 500s errors
[ http://issues.apache.org/struts/browse/SHALE-277?page=comments#action_38590 ]
Torsten Krah commented on SHALE-277:
------------------------------------
I would like to see this reopened.
As i wrote to the list, it does not work for me. I did integrate the use case example in my application, but when i hit the test pages submit button - the arithmetic exception is thrown - but a null pointer exception is thrown too, because my FacesContext dissapeared, i don't know why its gone - but its not there anymore after hitting the button to trigger the exception.
clay based exception trace snippet:
java.lang.NullPointerException: context
at javax.faces.component.UIComponentBase.getRenderer(UIComponentBase.java:738)
at javax.faces.component.UIComponentBase.getRendersChildren(UIComponentBase.java:307)
at org.apache.shale.clay.faces.ClayViewHandler.recursiveRender(ClayViewHandler.java:462)
at org.apache.shale.clay.faces.ClayViewHandler.renderView(ClayViewHandler.java:398)
at org.apache.shale.validator.faces.ValidatorViewHandler.renderView(ValidatorViewHandler.java:130)
at org.apache.shale.view.faces.ViewViewHandler.renderView(ViewViewHandler.java:147)
at de.sf.frc.jsf.navigation.LocaleViewHandler.renderView(LocaleViewHandler.java:86)
at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:384)
at javax.faces.webapp.FacesServlet.service(FacesServlet.java:138)
...
jsp based:
ERROR http-8080-Processor23 javax.faces.webapp.UIComponentTag - Faces context not found. getResponseWriter will fail. Check if the FacesServlet has been initialized at all in your web.xml.
ERROR http-8080-Processor23 org.apache.catalina.core.ContainerBase.[Catalina].[localhost].[/myapp].[jsp] - Servlet.service() for servlet jsp threw exception
java.lang.NullPointerException
at javax.faces.webapp.UIComponentTag.setupResponseWriter(UIComponentTag.java:929)
at javax.faces.webapp.UIComponentTag.doStartTag(UIComponentTag.java:310)
at org.apache.myfaces.taglib.core.ViewTag.doStartTag(ViewTag.java:70)
at org.apache.jsp.jsf.test_jsp._jspx_meth_f_view_0(test_jsp.java:100)
...
web.xml context param looks like this:
<context-param>
<param-name>
org.apache.shale.view.EXCEPTION_DISPATCH_PATH
</param-name>
<param-value>/jsf/error500.html</param-value>
</context-param>
The error page itself is displayed correct but empty if i call the page without an exception, so this should not be an issue.
Any help is welcome.
Torsten
> Shale is eating 500s errors
> ---------------------------
>
> Key: SHALE-277
> URL: http://issues.apache.org/struts/browse/SHALE-277
> Project: Shale
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0.3, 1.0.4-SNAPSHOT
> Environment: Tomcat 5.5.17 + Myfaces 1.1.3
> Reporter: Veit Guna
> Assigned To: Craig McClanahan
>
> When using shale-core for the s:token tag in my myfaces webapp, shale is eating 500 errors. That means if for example
> a Nullpointer Exception occurs, it doesn't let tomcat use the custom error page configured in the web.xml for 500 errors.
> If I remove shale-core from my webapp, everything works fine and the custom error-page is displayed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/struts/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira