DO NOT REPLY [Bug 18094] - validate method on ValidatorForm should use mapping.getName as key to validator

[bu...@apache.org]

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=18094>.
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=18094

validate method on ValidatorForm should use mapping.getName as key to validator

husted@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|struts-                     |husted@apache.org
                   |dev@jakarta.apache.org      |
   Target Milestone|---                         |1.2.1 Milestone
            Version|Nightly Build               |Unknown



------- Additional Comments From husted@apache.org  2003-03-18 10:42 -------
As it stands, this is the intended behavior. The formBean name is the default
attribute, but you can define a different attribute for an ActionMapping if need
be. So the validator was designed to see the attribute rather than the name. I
do see your point, but the API for 1.1 is locked, and (for good or ill) this is
how the API was designed to work. 

I agree that the behavior should be revisited in the next iteration, and so am
making this for the 1.2 family, first milestone. At that time, we should also
look at whether using the path as the identifer should be supported or
deprecated. Having two approaches is confusing, and we might want to decide and
declare the intent of the underlying API (FormBean.name vs
ActionMapping.attribute vs ActionMapping.path). 

-Ted.

---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org