Some issues relayed by Keith during recent travels...
0) Can we try to lighten up the composite a bit in the tooling? Something light blue/gray at about 30% opacity sounds about right.

1) Creating a bean service on a new project still fails to create the component definition in switchyard.xml. I think Rob determined that this was a dependency issue where the component-bean dependency was not added at some stage and so the config creation failed. Not sure if it's fixed or not, so disregard if it's a known and unresolved issue.

2) If I click on properties for a component and then update the component name and click OK, the name change does not take effect. If I follow the same procedure, but tab off of the name input before clicking OK, then it takes.

3) The component properties page has a contract section which lists security and transaction policy. Do we want this on component?

4) The component service transaction policy options are wrong. It should show interaction policies (propagates, suspends, etc.), but shows implementation policies instead.

5) The dirty flag is set after clicking OK on properties even if nothing was changed (e.g. open and immediately close = dirty).