while reading the discussions about upcoming cdi 2.0 features, I recognized that more and more features (interceptors, CDI-110) are based on some defined "binding" mechanism.

I am asking myself whether the currently bean binding mechanism is going to be generalized and published as part of some API (e.g. lifecycle events) in the near future? Doing so would 

1. benefit extension providers have a solid and standardized base for their binding based extensions

2. allow application developers to modify the binding during application startup e.g. by interacting with the thrown lifecycle events.

br, Sven