Oki, I think I found the solution and remove the complexity again.
Thread closes so far ;) LieGrue, strub ----- Original Message ----- > From: Mark Struberg <[email protected]> > To: deltaspike <[email protected]> > Cc: > Sent: Thursday, June 28, 2012 8:33 AM > Subject: @DefaultConfiguration yes/no ? > > Hi folks! > > I need an opinion about the @DefaultConfiguration. > > First, why did I add it? > Previously the LocaleResolver, ... have been @Typed and created with new > DefaultLocaleResolver(). You also could only change the default behaviour by > setting it into the MessageContext. Which means you needed to do this for > every > message creation :/ > > There have been a few TestSpecialLocaleResolver (and other config stuff) > which > got created in a CDI manner as @ApplicationScoped beans. Thus I was not able > to > change default handling to CDI without getting an > AmbiguousResolutionException. > As a quick solution I introduced the @DefaultConfiguration qualifier. > > But thinking about this a big longer, I think we don't need it, do we? > A user could also just introduce his own Qualifier and resolve the > AmbiguousResolutionException that way... > > Now that I have more clue about what is really needed in messaging, I think > we > can ditch the @DefaultConfiguration again, wdyt? > > LieGrue, > strub >
