I managed to solve most of the problem described here, hence a new topic for the remaining problem:
Is there a way to enable/disable @Decorators at runtime or during deployment? I can't just veto() them in my extension's
method because the container will complain about a missing bean while parsing the
section of the beans.xml
Hmmm, the first thing that comes to my mind would be a more configurable decorator (one that could actually not decorate, if configured as such -- if this is doable), which you then enable/disable/modify wrt Extension.