32  * by <code>SQLException</code>, a <code>SQLClientInfoException</code> provides a list of client info
  33  * properties that were not set.
  34  *
  35  * Some databases do not allow multiple client info properties to be set
  36  * atomically.  For those databases, it is possible that some of the client
  37  * info properties had been set even though the <code>Connection.setClientInfo</code>
  38  * method threw an exception.  An application can use the <code>getFailedProperties </code>
  39  * method to retrieve a list of client info properties that were not set.  The
  40  * properties are identified by passing a
  41  * <code>Map&lt;String,ClientInfoStatus&gt;</code> to
  42  * the appropriate <code>SQLClientInfoException</code> constructor.
  43  *
  44  * @see ClientInfoStatus
  45  * @see Connection#setClientInfo
  46  * @since 1.6
  47  */
  48 public class SQLClientInfoException extends SQLException {
  49 
  50 
  51 
  52 
  53         private Map<String, ClientInfoStatus>   failedProperties;
  54 
  55         /**
  56      * Constructs a <code>SQLClientInfoException</code>  Object.
  57      * The <code>reason</code>,
  58      * <code>SQLState</code>, and failedProperties list are initialized to
  59      * <code> null</code> and the vendor code is initialized to 0.
  60      * The <code>cause</code> is not initialized, and may subsequently be
  61      * initialized by a call to the
  62      * {@link Throwable#initCause(java.lang.Throwable)} method.
  63      *
  64      * @since 1.6
  65      */
  66         public SQLClientInfoException() {
  67 
  68                 this.failedProperties = null;
  69         }
  70 
  71         /**
  72      * Constructs a <code>SQLClientInfoException</code> object initialized with a

  32  * by <code>SQLException</code>, a <code>SQLClientInfoException</code> provides a list of client info
  33  * properties that were not set.
  34  *
  35  * Some databases do not allow multiple client info properties to be set
  36  * atomically.  For those databases, it is possible that some of the client
  37  * info properties had been set even though the <code>Connection.setClientInfo</code>
  38  * method threw an exception.  An application can use the <code>getFailedProperties </code>
  39  * method to retrieve a list of client info properties that were not set.  The
  40  * properties are identified by passing a
  41  * <code>Map&lt;String,ClientInfoStatus&gt;</code> to
  42  * the appropriate <code>SQLClientInfoException</code> constructor.
  43  *
  44  * @see ClientInfoStatus
  45  * @see Connection#setClientInfo
  46  * @since 1.6
  47  */
  48 public class SQLClientInfoException extends SQLException {
  49 
  50 
  51 
  52         @SuppressWarnings("serial") // Not statically typed as Serializable
  53         private Map<String, ClientInfoStatus>   failedProperties;
  54 
  55         /**
  56      * Constructs a <code>SQLClientInfoException</code>  Object.
  57      * The <code>reason</code>,
  58      * <code>SQLState</code>, and failedProperties list are initialized to
  59      * <code> null</code> and the vendor code is initialized to 0.
  60      * The <code>cause</code> is not initialized, and may subsequently be
  61      * initialized by a call to the
  62      * {@link Throwable#initCause(java.lang.Throwable)} method.
  63      *
  64      * @since 1.6
  65      */
  66         public SQLClientInfoException() {
  67 
  68                 this.failedProperties = null;
  69         }
  70 
  71         /**
  72      * Constructs a <code>SQLClientInfoException</code> object initialized with a