Why does the javax.crypto.spec.SecretKeySpec create an exception eagerly
in a static?
> private static final IllegalArgumentException BADPARAMS_EXC =
> new IllegalArgumentException(
> "algorithm is null or key is null, empty, or too short.");
If the exception is thrown it is not going to have a useful stack to
help debug the cause of the bad parameters.
Regards,
Tim
Mark Hindess (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/HARMONY-250?page=all ]
>
> Mark Hindess updated HARMONY-250:
> ---------------------------------
>
> Attachment: disambiguate.error.messages.diff
>
> Patch to split some error messages in to more less ambiguous messages.
>
>
>> disambiguate some error messages
>> --------------------------------
>>
>> Key: HARMONY-250
>> URL: http://issues.apache.org/jira/browse/HARMONY-250
>> Project: Harmony
>> Type: Improvement
>> Components: Classlib
>> Reporter: Mark Hindess
>> Priority: Trivial
>> Attachments: disambiguate.error.messages.diff
>>
>> As discussed on the -dev list, some exceptions are too ambiguous. I will attach
a patch to fix some of them.
>
--
Tim Ellison (t.p.ellison@gmail.com)
IBM Java technology centre, UK.
|