struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Benedict (JIRA)" <j...@apache.org>
Subject [jira] Updated: (STR-786) Make error more specific
Date Wed, 04 Jul 2007 02:56:27 GMT

     [ https://issues.apache.org/struts/browse/STR-786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Paul Benedict updated STR-786:
------------------------------

    Fix Version/s: 1.4.0
          Summary: Make error more specific  (was: Make error keys more specific)

> Make error more specific
> ------------------------
>
>                 Key: STR-786
>                 URL: https://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
>             Fix For: 1.4.0
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message