At one point, I thought that scope was implicit in such a context, so page.errorMessage, request.errorMessage, etc. was intended to work. Perhaps I am remembering that incorrectly :)
- jeremiah > -----Original Message----- > From: Eddie O'Neil > Sent: Thursday, September 08, 2005 9:10 AM > To: Beehive Developers > Subject: Re: [jira] Created: (BEEHIVE-911) error.jsp is using the wrong > scope for finding error messages > > > Wow -- good catch. Can't believe we've not run into that before. > > :) > > > > Daryl Olander (JIRA) wrote: > > error.jsp is using the wrong scope for finding error messages > > ------------------------------------------------------------- > > > > Key: BEEHIVE-911 > > URL: http://issues.apache.org/jira/browse/BEEHIVE-911 > > Project: Beehive > > Type: Bug > > Components: NetUI > > Versions: V1 > > Reporter: Daryl Olander > > Assigned to: Daryl Olander > > Priority: Minor > > Fix For: TBD > > > > > > In the Error.jsp page we are using ${request.errorMessage} to output the > errorMessage. I believe this should be ${requestScope.errorMessage}. > >
