All,
Boy, what a nice list.
I am not going to get discouraged. Struts is still, in my view, up there with
sliced bread. I will keep trying to fix this and then I'll watch these lists
like a hawk for anyone with the same problem so I can spare them the agony. It's
more painful when you find a problem with something you love. (Am I getting
carried away, now?)
Anyway, WB, I think you expect that I have 1.1 running. Correct me if I'm wrong,
but I thought the message-resource parm in the config.xml was only good in 1.1.
As I mentioned, I am running 1.02. Please let me know.... I'm probably going to
drop this until I can port my (error-message-less) application over to 1.1b.
(Fortunately, the app is only going to be used in a small technical setting, so
I can get away with this.)
Thanks hugely.
P.S.: But keep the help coming. Once I get this solved, I'm almost motivated to
write a comprehensive FAQ on the Error/Message processing in Struts. I think it
is badly needed.
[EMAIL PROTECTED] on 08/13/2002 01:10:24 PM
Please respond to "Struts Users Mailing List" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc: (bcc: Joseph Sadove/DKBDS USA/DKB)
Subject: RE: nulls (and only nulls) in <html:errors/>
I second the don't let it kill your opinion. I've had lots of issues in
this area, but it was always something I was doing wrong and once it was
fixed it was rock solid
I think I got the nulls once before. I am not that familiar with the
1.0x series, so this may not work under that. Try adding:
The null="false" to your message-resource like so:
<message-resources parameter="applicationresources" null="false"/>
When you run it see if you get ??keyname.thingee?? on screen.
Lemme know
-----Original Message-----
From: jsadove [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 13, 2002 12:49 PM
To: struts-user
Subject: RE: nulls (and only nulls) in <html:errors/>
Keith, Fabio,
Thanks much. I tried adding the errors.footer, errors.header keys but,
unfortunately, it didn't work. (BTW, yes I did bounce Tomcat each time
and
verify in the log file that the properties file was correctly loaded)
PLEASE, anyone who can give further help. I'm getting deperately
frustrated and
frustratingly desperate. It seems like such a simple thing, but
fraught with so many problems.
I tried the following variations (complete contents of properties file):
VARIATION 1:
errors.footer=</ul><hr>
errors.header=<h3><font color="red">Validation Error</font></h3>You must
correct
the following error
(s) before proceeding:<ul>
error.applname.required=<li>Application Name is required</li>
error.appldesc.required=there is nothing here
VARIATION 2:
errors.header=
errors.footer=
error.applname.required=<li>Application Name is required</li>
error.appldesc.required=there is nothing here
VARIATION 3:
error.applname.required=<li>Application Name is required</li>
error.appldesc.required=there is nothing here
errors.header=
errors.footer=
I have also been using GLOBAL_ERROR instead of a property name, since
these
errors should appear at the top of the page and not associated with
any field:
errors.add(ActionErrors.GLOBAL_ERROR, new
ActionError("error.applname.required"));
"Kamholz, Keith (corp-staff) USX" <[EMAIL PROTECTED]> on 08/13/2002
11:28:29 AM
Please respond to "Struts Users Mailing List"
<[EMAIL PROTECTED]>
To: "'Struts Users Mailing List'" <[EMAIL PROTECTED]>
cc: (bcc: Joseph Sadove/DKBDS USA/DKB)
Subject: RE: nulls (and only nulls) in <html:errors/>
Do you have errors.header and errors.footer defined in your properties
file?
~ Keith
http://www.buffalo.edu/~kkamholz
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 13, 2002 11:27 AM
To: [EMAIL PROTECTED]
Subject: nulls (and only nulls) in <html:errors/>
I am running 1.02 of Struts on Tomcat 4.04.
I get nulls returned to my JSP when trying to set errors in an
ActionForm.
I have scoured the mailing lists and have found lots of people getting
nulls
on
either side of the error strings (apparently a Weblogic thing)
and there are people getting nothing, seemingly no one getting the
string
"null".
I will be vastly grateful to anyone who can help.
(Until this problem, I have thought struts --with Arron Bates nested
extensions-- were right up there next to sliced bread. Please help me
preserve the glow!)
I've appended below all the useful bits of code, I think.
Here are the contents of ApplicationResources.properties file:
error.applname.required=<li>Application Name is required</li>
error.appldesc.required=there is nothing here
Here are the relevant parts of the struts config file:
BEGIN CODE
<!-- bean definition -->
<form-beans>
<form-bean name="NewApplicationBean"
type="dkb.irmis.struts.beans.NewApplicationBean" />
....
</form-beans>
<!-- forwards -->
...
</global-forwards>
<!-- actions -->
<action-mappings>
....
<action path="/NewApp" type="dkb.irmis.struts.actions.NewAppAction"
name="NewApplicationBean"
input="/new_application.jsp"
scope="session">
<forward name="newappform" path="/new_application.jsp"/>
</action>
....
</action-mappings>
</struts-config>
END CODE
And here is the validate method:
BEGIN CODE
public ActionErrors validate(ActionMapping mapping,
HttpServletRequest
request) {
ActionErrors errors = new ActionErrors();
if (addApplications.equals("ADD Applications") ) {
addApplications = "RESET Values";
for (int i = 0; i < applicationList.size(); i++) {
if (
((NewApplicationObj)applicationList.get(i)).getApplicationDesc().length(
) >
0 )
{
if(
((NewApplicationObj)applicationList.get(i)).getApplicationName() == null
||
((NewApplicationObj)applicationList.get(i)).getApplicationName().length(
) <
1 )
{
errors.add("applname", new
ActionError("error.applname.required") );
}
}
}
}
if ( errors.empty() ) {
return null;
}
return errors;
} // end validate
END CODE
--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail:
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail:
<mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
