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/03/23 18:53:49 UTC
DO NOT REPLY [Bug 7393] New: -
struts-example: parameter substitution doesn't work in exception messages
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=7393>.
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=7393
struts-example: parameter substitution doesn't work in exception messages
Summary: struts-example: parameter substitution doesn't work in
exception messages
Product: Struts
Version: 1.1 Beta 1
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: Normal
Priority: Other
Component: Example
AssignedTo: struts-dev@jakarta.apache.org
ReportedBy: matt@raibledesigns.com
In struts-config.xml contains the following for the /logon action:
<exception key="expired.password"
type="org.apache.struts.webapp.example.ExpiredPasswordException"
path="/changePassword.jsp"/>
I changed the expired.password key from:
expired.password=User Password has expired
to:
expired.password=User Password has expired for {0}
By doing this, I expected the "username" would be substituted for {0} since
PasswordExpiredException has this line:
super("error.password.expired", username);
1. It doesn't seem like the key "error.password.expired" is ever being used in
PasswordExpiredException, since "expired.password" is the one being used.
2. If I add a {0} parameter to either key, neither one is substituted with
the "username" value.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>