I also believe this is intentional, BeanConfigurator interface is made for adding synthetic beans and those don't even need to be backed by real classes, therefore no observer method "discovery" happens within that bean. If you wish to register an OM too, then you can do that within the same extension lifecycle observer - AfterBeandiscovery#addObserverMethod().
We should probably file a spec issue.
Do you mean a TCK one? I am not sure this this would be worth a spec text one - I feel like it's kind of implied that synthetically specified bean won't be scanned for OM (or producers, disposers etc), it might be just me though |