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/07/27 19:20:42 UTC
DO NOT REPLY [Bug 21913] New: -
Reloading a Struts app doesn't update form bean definitions
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=21913>.
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=21913
Reloading a Struts app doesn't update form bean definitions
Summary: Reloading a Struts app doesn't update form bean
definitions
Product: Struts
Version: 1.1 Final
Platform: PC
OS/Version: FreeBSD
Status: NEW
Severity: Normal
Priority: Other
Component: Controller
AssignedTo: struts-dev@jakarta.apache.org
ReportedBy: milo@cyberlifelabs.com
When reloading a Struts app via 'ant reload', changes made to form bean definitions seem to
go unnoticed. Performing a hard reload (i.e. 'ant remove' followed by 'ant install') causes the
changes to take effect.
The problem can be duplicated as follows:
1) Create a form bean with one property.
2) Create an action-mapping that uses the form bean.
3) Create a JSP that uses <html:form> to post to the action-mapping and <html:text> to
reference the property in the form bean.
4) Build, install and test the app. All should be fine thus far.
5) Add another property to the form bean.
6) Add another <html:text> to the JSP that references the new property.
7) Rebuild, reload and test the app. It should throw an exception complaining that the getter
method for the new property cannot be found.
8) Remove, re-install and test the app. Should work now.
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org