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/04/22 17:13:22 UTC
DO NOT REPLY [Bug 8369] New: -
enhancement request : specifying abstract or interface FormBeans
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=8369>.
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=8369
enhancement request : specifying abstract or interface FormBeans
Summary: enhancement request : specifying abstract or interface
FormBeans
Product: Struts
Version: 1.1 Beta 1
Platform: All
OS/Version: All
Status: NEW
Severity: Enhancement
Priority: Other
Component: Controller
AssignedTo: struts-dev@jakarta.apache.org
ReportedBy: ndeloof@capgemini.fr
Struts current version has the limitation that you have to specify a concrete
class for formBean in mapping declaration (struts-config.xml). This limitation
seem's to come from the way ActionServlet tests the class of curent FormBean in
scope to know if it has to instanciate a new one : the test uses the class name.
Using a Class object obtained from declared name, with isInstance() test (or
another reflect mecanism) would allow :
1. Have the form bean subclass an abstract form bean,
2. have the form bean implement a form bean interface you define, or
3. specify a specific class name (as actual behaviour)
Overhead could be limited by using a cache mecanism, the same way Struts look
for Action classes as needed.
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>