commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 34103] - [configuration] Inconsistent behavior
Date Tue, 22 Mar 2005 08:24:41 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=34103>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=34103





------- Additional Comments From ittayd@qlusters.com  2005-03-22 09:24 -------
i use the converters in commons beanutils. works very nicely.

i'd also use commons el for the interpolation. 

about not throwing an exception: 1. this is where the mandatory vs. optional
difference comes to play. if a client wants null when the property doesn't
exist, it means the code can handle such a case --> this is an optional property
--> he should use getProperty(key, null). however, having the flag can be
syntactic sugar (in the sense that it means that getProperty(key) will be
treated as getProperty(key, null)). so it doesn't hurt.



-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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


Mime
View raw message