We rebuilt the binding component from scratch and did not get the error this time. What we did wrong the first time still remains unresolved.
If we find out we will post our solution here. In the meantime if you are facing the same issue all I can say to you is restart from the beginning with perhaps the hello world example at the servicemix website and try to get that up and running first.
We suspect that the pom.xml for the custom bc component was containing an error in the namespace creation. How this effected the xbean in runtime is not well understood at the moment but it may be this which caused the error. Hopefully if you have the same problem this info might help you.
Good luck with your ESB good folks!
Error was likely here ->
Turns out while using Eclipse autogenerated author comment, the xbean namespaces will be confused.
For instance in your endpoint.java class you may have something looking like this at the top of your class:
/ * @org.apache.xbean.XBean element="connection"
/ * /
/* @Author da25
This caused the above error for us.
Solution: Remove the autogenerated part @author da25 and the XBean will not be so upset anymore.