Hi, Gary.
Thanks for your feedbacks and sorry for delay.

IMO it sounds OK and we can live with your strategy.
I summarize it:
* child bean id is `foo$child.bar.handler` or `foo$child#2.handler`
* child componentName is `foo$child.bar` or `foo$child#2`
* we remove aliasing
* and strictly insist to declare 'id' on the `<chain>`, if end-user decide to use an 'id' for child components.
* we should fix https://jira.springsource.org/browse/INT-3009 ASAP.

And from big height it's our opinion around consistency and KISS, but the practice will show how it is useful...
Right now I need it to track handlers withing chain and have an ability to change their properties at runtime.
So, I wait your conclusion and go ahead.