I never really liked this idea. I think you should provide a concrete setPostalCode (String code) method and if the data is valid you would call setPostalCodeField (String code) or setPostalCode_(String code). I think this type of validation is part of the business logic. Alternatively, there are types of validation that are really an aspect (deployment environment specific). For example, a company specific mail route field. The validation of this field would depend on the deployment environment (which company it is deployed at). In this case I see an interceptor, possibly a Bean Scripting Framework interceptor.

What I am getting at is I think this proposed solution is a hack and I personally would not accept the patch, but the user community has convinced me to include things I consider hacks.

-dain

On Monday, January 27, 2003, at 08:31 AM, Themba Mbatha wrote:

Hi all;

What would be the procedure if one is interested in implementing a
feature request? There is a feature request (647669) that I also need
a.s.a.p. and I'm prepared to contribute the implementation once I'm
done.

Regards.





-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to