You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by bu...@apache.org on 2002/08/15 20:08:26 UTC
DO NOT REPLY [Bug 11733] New: -
Make error keys more specific
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11733>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11733
Make error keys more specific
Summary: Make error keys more specific
Product: Struts
Version: 1.1 Beta 2
Platform: Other
OS/Version: Other
Status: NEW
Severity: Enhancement
Priority: Other
Component: Unknown
AssignedTo: struts-dev@jakarta.apache.org
ReportedBy: dmkarr@earthlink.net
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.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>