Re: [cdi-dev] What to do to move CDI-30/PR 296 Forward
We have been burning our brains over this very topic, but it doesn't yet feel sound.
So I guess we will give it another few days/weeks to tinker with it.
The main downside of this api is that it's actually only useful for the request
context and only in SE. But we still add an API which looks to the user as it could use it
for e.g. the ConversationContext, or existing servlet requests etc. It's
complicated...
I think we will first incorporate the parts which we found really nice solutions for.
* Interceptor/Decorator for producer methods and custom Bean<T> implementations
* bean-discovery without automatically picking up all classes as @Dependent
* A few other minor tickets
Should not take that long. After that we will have to tackle CDI-30 for sure.
LieGrue,
strub
On Wednesday, 7 September 2016, 19:04, John Ament <john.ament(a)spartasystems.com>
wrote:
All,
It seems like we're still stuck on CDI-30. Its been open, last activity on Aug 2. I
would love to see it closed and only reference the use case agreed to - another library
wants to integrate CDI into its stack. To do so, it wants to be able to start and stop
the built in contexts.
John