You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Paul Benedict (JIRA)" <ji...@apache.org> on 2006/11/26 07:07:57 UTC
[jira] Updated: (STR-786) Make error keys more specific
[ http://issues.apache.org/struts/browse/STR-786?page=all ]
Paul Benedict updated STR-786:
------------------------------
Bugzilla Id: (was: 11733)
Component/s: Core
(was: Unknown)
Assignee: (was: Struts Developers)
> Make error keys more specific
> -----------------------------
>
> Key: STR-786
> URL: http://issues.apache.org/struts/browse/STR-786
> Project: Struts 1
> Issue Type: Improvement
> Components: Core
> Affects Versions: Nightly Build
> Environment: Operating System: other
> Platform: Other
> Reporter: David M. Karr
> Priority: Minor
>
> 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 {0}". From the ones I see near
> "formBean" in the ActionResources.properties file, there are many keys that are
> not specific at all.
--
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