Duplicate Proxy.newProxyInstance calls during PGXAConnection.getConnection? - Mailing list pgsql-jdbc

From Andy Fan
Subject Duplicate Proxy.newProxyInstance calls during PGXAConnection.getConnection?
Date
Msg-id CAKU4AWog5YvO7wOBQ7nyGhV5JAm2s9sLoANGJMuG6BjJbDPAKA@mail.gmail.com
Whole thread Raw
Responses Re: Duplicate Proxy.newProxyInstance calls during PGXAConnection.getConnection?  (Andy Fan <zhihui.fan1213@gmail.com>)
List pgsql-jdbc
In the PGXAConnection.GetConnection() [1], we can see the below code:

  @Override  public Connection getConnection() throws SQLException {
    // the first time ConnectionHandler has been created.    Connection conn = super.getConnection();   
    // When we're outside an XA transaction, autocommit    // is supposed to be true, per usual JDBC convention.    // When an XA transaction is in progress, it should be    // false.    if (state == State.IDLE) {      conn.setAutoCommit(true);    }
    /*     * Wrap the connection in a proxy to forbid application from fiddling with transaction state     * directly during an XA transaction     */
    // ConnectionHandler is created again here.     ConnectionHandler handler = new ConnectionHandler(conn);    return (Connection) Proxy.newProxyInstance(getClass().getClassLoader(),        new Class[]{Connection.class, PGConnection.class}, handler);  }

However I think the proxy has already been created at the first line: super.getConnection(), 
and then it is created later.  Is it a duplication? 

pgsql-jdbc by date:

Previous
From: Dave Cramer
Date:
Subject: [pgjdbc/pgjdbc] 05b129: Pull fixes for PR#2556 into master (#2826)
Next
From: Andy Fan
Date:
Subject: Re: Duplicate Proxy.newProxyInstance calls during PGXAConnection.getConnection?