Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <4509FCBC.2020800@apache.org>
Date: Thu, 14 Sep 2006 18:07:08 -0700
From: Daniel John Debrunner <djd@apache.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
 rv:1.7.3) Gecko/20040910
MIME-Version: 1.0
To: derby-dev <derby-dev@db.apache.org>
Subject: possible JDBC 4 EOD bug??
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I'm trying to understand the expected behaviour of the assignment of
columns from an EOD SQL @Select to a data class using JavaBeans style
property accessors. I'm looking at section "19.1.5 User Class" of JDBC 4.0.

I have a class similar to the example but a little different. The
difference is the private field name does not match the name of the
JavaBean property, is that allowed?

public class Person
{
  private String myName;

  public void setName(String name) {
     this.myName = name;
  }
  public String getName() {
     return myName;
  }
}

If my select returns a column called 'NAME' then it does not map to the
JavaBean property called 'name'. Instead the name of the column needs to
map to the name of the private field, 'myName'. Then the field is set
correctly but the setter is never used. Is this a bug, it seems like it?

Thanks,
Dan.