Now that I've started using JavaUtils.getMessage, I discovered that ParseException IS NOT a RuntimeException.  I was just listing it in the throws clause as a form of documentation, assuming it WAS a RuntimeException.  But it's not needed and it would require callers of getMessage to explicitly catch it, which is bad.  The javadoc for java.text.MessageFormat is a bit wrong and misled me.
Now that I've started using JavaUtils.getMessage, I discovered that ParseException
IS NOT a RuntimeException.  I was just listing it in the throws clause as a form of
documentation, assuming it WAS a RuntimeException.  But it's not needed and it
would require callers of getMessage to explicitly catch it, which is bad.  The javadoc
for java.text.MessageFormat is a bit wrong and misled me.


git-svn-id: 8699849808240b02471d01f5aaa03ec0c1cb68ee@252736 13f79535-47bb-0310-9956-ffa450edef68

apache/axis1-java,apache/axis1-java,apache/axis1-java,apache/axis1-java