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 2003/04/30 07:07:23 UTC
DO NOT REPLY [Bug 19458] New: -
User Guide ActionMapping example confuses Session/Request scope
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=19458>.
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=19458
User Guide ActionMapping example confuses Session/Request scope
Summary: User Guide ActionMapping example confuses
Session/Request scope
Product: Struts
Version: Nightly Build
Platform: Other
OS/Version: Other
Status: NEW
Severity: Enhancement
Priority: Other
Component: Documentation
AssignedTo: struts-dev@jakarta.apache.org
ReportedBy: phil@steitz.com
The ActionMapping Example
(http://jakarta.apache.org/struts/userGuide/building_controller.html#config) says,
"When a request that matches this path is received, an instance of the
LogonAction class will be created (the first time only) and used. The controller
servlet will look for a session scoped bean under key logonForm, creating and
saving a bean of the specified class if needed."
But the form in the example has request scope, so this is not correct. A new
form will be created for each request and added as a request attribute.
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org