Hello,

you should be able to just @Inject Application there.

What is the problem you are seeing, any exceptions?

Can you show some code?

Alright, so I see no really simple solution for this. You currently have four valid beans of that type and qualifiers won't cut it, so we need to look for way around that.

One way to solve it would be to create another @ConversationScoped bean, let's call it ApplicationHolder, and in this bean you would set the correct instance of Application implementation once you know it.

You could have the 4 implementations differed by qualifiers and select the right one, or you could just instantiate the impl yourself assuming you don't need injection there.

All access to Applicaiton would then have to be routed via ApplicationHolder which "knows" the correct instance.

Another way would be to have all implementation of Application @Vetoed and then create a @Produces Application method. This method would return a @ConversationScoped bean picking one of the implementations based on some settings it can discern from current state (e.g. setting some value based on what information user enters on first screen?)

Yet another solution coming to mind is a bit more hardcore-ish. You could leverage BeanManager and use it to grab the Context object (conversation context) - BeanManager#getContext().

Then you could use Context#get(Contextual<T>) to grab the instance itself. To obtain Contextual<T> you could either @Inject Bean<T> (since Bean extends Contextual) or use some more methods from BM.