[esb-issues] [JBoss JIRA] Commented: (JBESB-683) ListenerUtil.obtainAtt has different interpretation of default value for null
[ http://jira.jboss.com/jira/browse/JBESB-683?page=comments#action_12368852 ]
Tom Fennelly commented on JBESB-683:
------------------------------------
This was already sorted out on the ConfigTree class. It was the same - null caused and
exception if the property/attribute was not present. I changed it back (on ConfigTree) to
behave in the way 99.9999% of the world would expect i.e. as you outlined above. For
required attributes (to throw an exception) I added an explicit
"getRequiredAttribute" method.
ListenerUtil.obtainAtt has different interpretation of default value
for null
-----------------------------------------------------------------------------
Key: JBESB-683
URL: http://jira.jboss.com/jira/browse/JBESB-683
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Rosetta
Reporter: Mark Little
Assigned To: Mark Little
Fix For: 4.2
The normal assumption of null for a default value (e.g., in System.getProperty) is that
you return null if there is nothing set. However, in ListenerUtil, if you pass null as a
default value this means throw a ConfigurationException on finding null for the value.
This is not intuitive and goes against all other similar mechanisms. If we need this
capability, then let's add an explicit method for throwing an exception, or another
parameter.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira