No more boring boilerplate

Write something like:

 /** The name of this widget */
 public property String name;

instead of:

 /**
  * Gets the name of this widget
  * @return the name of this widget
  */
 public String getName() { return name; }
 /**
  * Sets the name of this widget
  * @param name the new name of this widget
  */
 public void setName(String name) { this.name = name; }

Nicer syntax for property access

Use short-hand field-like LHS and RHS syntax, such as:

 my.property = your.otherProperty;

instead of

 my.setProperty(your.getOtherProperty());

Other operators (such as -> or .@) have been proposed to distinguish property access from field access.

This link discusses the readability issue further: Bug 6180800.

Javadoc should document properties

We think of properties as something higher-level than the get/set method implementation, and Javadoc should reflect that. We’d like

• Fields
• Properties
• Constructors
• Methods

See this proposal by Mikael Grev.

Bound properties

Many bound property implementations are really boring. Set the new value, maybe check that it isn’t null, maybe check that it is different from the old value, then set it and fire the property change.

When you have lots of bound properties (like in Swing), you’d like to reduce this drudgery.

The difficulty is that not all bound property implementations are exactly identical. Maybe a null value is ok. Should one test for equality? Is this property an oddball case that cannot be handled mechanically?

Many solutions have been proposed. Some are based on annotations, others on generics, such as

 class Point {
   public property int x bound;
   public property int y bound;

   private <T> void propertyChange(Property<Point, T> prop, T oldValue, T newValue) {
     // do what you want here
    }
 }

Proposed by Remi Forax.

Get list of properties using core reflection (not JavaBeans) API

Properties are design features, and the get/set patterns are just an implementation detail. The design intent should be discoverable by runtime tools, in particular, core reflection.

This is proposed by Remi Forax.

 public class Class<T> {
   public Property<T, ?>[] getProperties() {}
   public Property<T, ?> getProperty(String name) {}
 }

Avoid annotation ambiguity

In EJB3, you annotate persistent properties. But to annotate fields or getters, that is the question.

 @Id
 private int id;

or

 @Id
 public int getId() { ... }

Why should this be an issue? The developer just wants to annotate the property:

 public property int id;

Statically-verifiable property literals (for use in beans-binding and property reflection)

Expose Property/PropertyDescriptor objects through language syntax, which enables the compiler to validate that the property actually exists.

Syntax proposals abound:

• Bean.name
• Bean#name also here
• Bean@name
• Bean->name
• Bean:name

Consider this example which binds the currentPrice property of the visualControl object to the value of the price property of the dataSource object.

binding = Bindings.createAutoBinding(
  AutoBinding.UpdateStrategy.READ_WRITE,
  dataSource,
  ELProperty.create("${price}"),
  updatedControl,
  BeanProperty.create("currentPrice"));

If the currentPrice property is renamed, the above code will break and refactoring tools will not be able to catch it. With property literal syntax the above code looks like this:

binding = Bindings.createAutoBinding(
  AutoBinding.UpdateStrategy.READ_WRITE,
  dataSource,
  ELProperty.create("${price}"),  // see ^ note below
  updatedControl#currentPrice);

This idea (paraphrased here in Beans Bindings 1.0 code) originally came from Stephen Colebourne.

^ Note that the price property reference within the Unified EL expression still suffers from the same problem. Reifying this is an entirely different problem - support for lambda expressions with a code-as-data view ala C# 3.0 would be required.

Use a switch statement to select property in generic property (change) listeners

Remi Forax proposal.

 Bean bean=new Bean();
 bean.addPropertyListener(new PropertyListener<Bean>() {
   public <T> propertyChanged(Property<Bean, T> property, T oldValue, T newValue) {
     switch(property) {
       case name:
         frame.setTitle((String)newValue);
         break;
       case value:
         slider.setValue((Integer)newValue);
         break;
     }
   }
 }

Ignore nulls in a chain of accessors

input.address.postcode; // returns null if input.address is null

mentioned here.

Property Inspection during Debugging

Properties can be listed along with fields in a debug “Watch” or “Locals” view.

The Visual Studio 2008 Locals view for example shows by default only public members (mostly properties) with non-public members hidden in a subtree, which can be expanded to view those members if necessary.