struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Benedict (JIRA)" <>
Subject [jira] Resolved: (STR-1730) [taglib] "Cannot find bean * in scope null" ==> increase error specificness
Date Wed, 04 Jul 2007 05:14:26 GMT


Paul Benedict resolved STR-1730.

       Resolution: Won't Fix
    Fix Version/s:     (was: 1.4.0)

The issue is a relic of its time. The function of knowing what line in an JSP is erring belongs
to the container, not a framework -- unless the framework has template parsing abilities like
Tapestry or Wicket. Therefore, users should be happy to know that the newer versions of Tomcat
do just that. They do "line precise error reporting" which prints the snippet of markup (with
a couple lines before and after) in error.

> [taglib] "Cannot find bean * in scope null"  ==> increase error specificness
> ----------------------------------------------------------------------------
>                 Key: STR-1730
>                 URL:
>             Project: Struts 1
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.0 Final
>         Environment: Operating System: other
> Platform: Other
>            Reporter: Ralf Hauser
>            Priority: Minor
> When I am getting stack traces like
> <<org.apache.jasper.JasperException: Cannot find bean user in scope null
> 	at org.apache.jasper.servlet.JspServletWrapper.service(
> ...
> root cause
> javax.servlet.ServletException: Cannot find bean user in scope null
> 	at
> org.apache.jasper.runtime.PageContextImpl.handlePageException(
> 	at org.apache.jsp.userprofile_en_jsp._jspService(
> ...>>
> it would be really helpful to know where it happened in the jsp page.
> There might be dozens of struts tags referring to "user" and from the
> *, it is often not very obvious which one it is.
> Therefore, my RFE is to have the exception provide more hints on where it fails
> - best by citing the offenting struts-tag!

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message