Gerhard,
Thx for the info, it works. However, i have a few remarks about the
solution:
Creating a new producer method with another qualifier specification,
requires that you change your already defined injection points. (if you
decide in the middle of the development phase that you need some
hi rudy,
basically you could provide an alternative producer implementation.
however, +1 for your suggestion. we have to think about the details. if we
allow a list of message-handlers, we would have to ignore the qualifiers in
this case - i would prefer only one optional custom implementation
Hi all,
I like to register a new MessageHandler in CODI but it gets never called.
On the wiki page (1) I found a description how this could be done. I placed
the line of code within a method that observes for StartupEvent like this
@Inject
private MessageContext context;
public
hi rudy,
the producer for the message-context with the @Jsf qualifier creates a
dependent instance.
since the default implementation (without qualifier) doesn't specify a scope
(because it's independent of cdi), it's automatically a dependent bean.
that means: you can't use the startup event in
