RFR 8058778: New APIs for creating certificates and certificate requests

[Wang Weijun]

> On Jan 13, 2016, at 9:51 PM, David M. Lloyd <david.lloyd at redhat.com> wrote:
> 
>> The current behavior is that it will consume one ----BEGIN...END---- block (with optional text before the block) or one DER SEQUENCE, or undefined if no such data structure are found. However, I am not sure if I need to document that as a requirement. Do you want any guarantee?
> 
> I think it's probably a good idea to at least document what happens in the event of various errors.

* <p>If an unsupported {@code type} is provided, an
* {@link IllegalArgumentException} will be thrown and {@code inStream}
* will not be consumed. If a parsing error is encountered, a
* {@link CertificateException} will be thrown and the read position of
* {@code inStream} is undefined.

--Max