Details
Description
When I'm trying to track through the Struts source code to find out where an
error message is being emitted, after I find the display string in the
properties files, I then have to search for the given key in the source code.
It would be very convenient if the key associated with that display string was
specific enough to be reasonably certain that it wouldn't occur hundreds of
times in unrelated places. Unfortunately, for several (most?) of these error
keys, that is not the case. A perfect example: "formBean". That's the error
code for "Error creating form bean of class
". From the ones I see near
"formBean" in the ActionResources.properties file, there are many keys that are
not specific at all.
Attachments
Issue Links
- depends upon
-
STR-423 Struts fails silently in too many places
- Reopened
-
STR-1638 MalformedURLException: You must specify exactly one of "forward", "href", or "page"
- Resolved
-
STR-1730 [taglib] "Cannot find bean * in scope null" ==> increase error specificness
- Resolved
-
STR-1809 Enhance log error message for when the Action cannot instantiate
- Resolved
-
STR-1819 Warn if a form is not declared but used by an action
- Resolved
-
STR-2020 Improve error detail when form validation fails from absent ActionServlet
- Resolved
-
STR-2153 Report the bean and property name when iteration fails
- Resolved
-
STR-2173 Better error message for "Exception thrown by getter for property"
- Resolved
-
STR-2437 Standardize exception rethrows to contain root cause
- Resolved
-
STR-2611 Cite the form name in validation exception message
- Resolved
-
STR-3094 Emit error to log when input forward does not exist
- Resolved
-
STR-1808 Warn if an Action path string appears twice in configuration
- Closed