[STR-1730] [taglib] "Cannot find bean * in scope null" ==> increase error specificness

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: 1.0.0
• Component/s: Core
• Environment: Operating System: other; Platform: Other
• Bugzilla Id: 22935
• Assignee: Unassigned
• Reporter: Ralf Hauser
• Created: 04/Sep/03 22:26
• Updated: 02/May/13 02:28
• Resolved: 04/Jul/07 05:13

Description

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(JspServletWrapper.java:254)
...
root cause

javax.servlet.ServletException: Cannot find bean user in scope null
at
org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImpl.java:533)
at org.apache.jsp.userprofile_en_jsp._jspService(userprofile_jsp.java:124)
...>>
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
*_jsp.java, 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!

Issue Links

• is depended upon by: STR-786 Make error messages more specific (omnibus issue)