Component update

The components in the Aria framework inherited the XUI design, which makes them a bit non standard. Starting with v4.0 Aria will resolve this problem by dropping the AttributedComponent interface in favour of the normal beans API.

While this will make the API a little fatter it will mean that component construction and setup will be that much simpler as a single interface can be used. A single interface will also mean that the builder and factory components can be significantly simplified, along with the component adapters. The change will also bring the component properties setup more into line with the common registration mechanism used for data bindings, events and so on within Aria.

However for backward compatibility and for MIDP support (where reflection is not available) a set of helper classes will be created to enable an equivalent of the AttributedComponent interface to be used. Initially a set of AttributeHelper classes implement the replacement methods for the setAttribute interfaces, but moving forward a more flexible, pluggable interface will be needed.

One added advantage of switching the component interface is that third party components can more easily be used as normally they comply with the beans specification. Yet to take full advantage of this the editor plugins and the component registration/adapter mechanism will need some minor updating along with the jar referencing.