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/06/05 14:47:37 UTC
DO NOT REPLY [Bug 9624] New: -
RequestActionMapping init-param to ActionServlet
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=9624>.
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=9624
RequestActionMapping init-param to ActionServlet
Summary: RequestActionMapping init-param to ActionServlet
Product: Struts
Version: 1.1 Beta 1
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Component: Controller
AssignedTo: struts-dev@jakarta.apache.org
ReportedBy: husted@apache.org
Although only deprecated, this does not seem to use the class specified (e.g.
org.apache.struts.action.RequestActionMapping). The className alternative does
work. I do think it would be great if we could retain this functionality
instead of deprecating it, since specifying the className each time seems like a
pain. In effect, deprecating this also deprecates RequestActionMapping, since
the functionality overlaps with scope="request". Personally, I would vote to
retain both. I like the className functionality, but I also like the idea of
being able to make a global change. I haven't checked the other init-params yet.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>