I thought I showed this to Ales at OpenBlend.
Yup. :)
And we also already tried to do this (to some extent) within AS6+OSGi.
So, Sahoo, afaiu you're simply making this CDI extension available to every deployment; e.g. putting it dynamically on the classpath,
and Weld' extension handling does all the rest?
This sounds like the right way to do it, *but* how do you then tie-in the actual extension instance into app. server' container?
Since afaik, the instance is created by Weld internals, which knows nothing about your custom app server container.
Or is there already some hook available in Weld wrt extensions handling in diff env/containers?