y 17, 2013 11:09:49 AM GMT +00:00 GMT Britain,
Ireland, Portugal
Subject: And Decoder (was Re: No newline at the end of
Base64.getMimeEncoder())
This time on the decoder side:
Base64.getMimeDecoder().decode("AA==\n")
throws an exception because the string ends with a newline. I would
pr
ted that Base64.getMimeDecoder().decode("\n")
doesn't throw an exception.
regards
Mark
- Original Message -
From: weijun.w...@oracle.com
To: core-libs-dev@openjdk.java.net
Sent: Thursday, January 17, 2013 11:09:49 AM GMT +00:00 GMT Britain,
Ireland, Portugal
Subject:
rom: weijun.w...@oracle.com
To: core-libs-dev@openjdk.java.net
Sent: Thursday, January 17, 2013 11:09:49 AM GMT +00:00 GMT Britain, Ireland,
Portugal
Subject: And Decoder (was Re: No newline at the end of Base64.getMimeEncoder())
This time on the decoder side:
Base64.getMimeDecoder().decode("AA=
java.net
Sent: Thursday, January 17, 2013 11:09:49 AM GMT +00:00 GMT Britain, Ireland,
Portugal
Subject: And Decoder (was Re: No newline at the end of Base64.getMimeEncoder())
This time on the decoder side:
Base64.getMimeDecoder().decode("AA==\n")
throws an exception because the stri
This time on the decoder side:
Base64.getMimeDecoder().decode("AA==\n")
throws an exception because the string ends with a newline. I would
prefer it be acceptable.
Thanks
Max
On 01/17/2013 05:12 PM, Weijun Wang wrote:
I noticed that the encoding output of Base64.getMimeEncoder() never en
I noticed that the encoding output of Base64.getMimeEncoder() never ends
with a newline char. There is no right or wrong on this but it will be
nice to write the current behavior into the spec.
Thanks
Max
