[ https://issues.apache.org/struts/browse/STR-1730?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Benedict updated STR-1730:
-------------------------------
Fix Version/s: 1.4.0
Assignee: (was: Struts Developers)
> [taglib] "Cannot find bean * in scope null" ==> increase error specificness
> ----------------------------------------------------------------------------
>
> Key: STR-1730
> URL: https://issues.apache.org/struts/browse/STR-1730
> Project: Struts 1
> Issue Type: Improvement
> Components: Core
> Affects Versions: 1.0 Final
> Environment: Operating System: other
> Platform: Other
> Reporter: Ralf Hauser
> Priority: Minor
> Fix For: 1.4.0
>
>
> 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!
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
|