Content-Type: multipart/related; boundary="------------010704000401050304040909" --------------010704000401050304040909 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit Hi,

Issue #245: https://github.com/ThreeTen/threeten/issues/245
suggests that a more specific exception be used for cases
where the field or units or values are unsupported or invalid.

I expect that with some review, the criteria for using the new exception
vs DateTimeException and the addition of @throws UnsupportedTemporalTypeException
will need to be refined.

It may be preferable to put the detailed exception into the java.time.temporal
package since developers would normally only need to be using DateTimeException
if they were catching exceptions.

javadoc: http://cr.openjdk.java.net/~rriggs/javadoc-temporaltypeexception-245/

webrev: http://cr.openjdk.java.net/~rriggs/webrev-temporaltypeexception-245/

Please review and comment.

--
Thanks, Roger

Oracle Java Platform Group

Green
            Oracle Oracle is committed to developing practices and products that help protect the environment

--------------010704000401050304040909 Content-Type: image/gif; name="green-for-email-sig_0.gif" Content-Transfer-Encoding: base64 Content-ID: Content-Disposition: inline; filename="green-for-email-sig_0.gif" R0lGODlhLAAcAMQAAP///0x9RHmec9Pf0aa+oleFULHGrmKNW+nv6I+uivT39N7n3W6VZ7zP uZu2lsjXxYSmfwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA ACH5BAAAAAAALAAAAAAsABwAQAXhICCOZGmeaDoaReC+sKAMR7GopIA6boIvLgPAVSAgALxj SYdrOp/Q6NPgYqIEPkTBV2taTwgGbEw+PAZo3FfKbqMQQfeJ8DoY0Hg0wxhAKBgHCl5XLgMq DwFCAAIFPIYDgidrOUQGkSh0cQMJAQyXOXKhoqOkpaanI2aoIwMErq+uCY0BMlANKpxkYwQG BH82TpMicD0pAgQACToDAchqhAG3KQ4HIlQNnErG0IYqB9EAiEQvwEsozC43hy0CAeXMwsLD LS8MAvf497ruCZ+gOA0gfNt3AIK0J/JWKVzIsEQIADs= --------------010704000401050304040909--