Re: [cdi-dev] What to do to move CDI-30/PR 296 Forward

That's kind of an odd response. How does CDI-30 only work for request context? What makes you believe that? Same for SE only. John ________________________________ From: Mark Struberg <struberg(a)yahoo.de&gt; Sent: Wednesday, September 7, 2016 4:08 PM To: John Ament; Cdi-dev Subject: 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&gt; wrote: ________________________________ NOTICE: This e-mail message and any attachments may contain confidential, proprietary, and/or privileged information which should be treated accordingly. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this message, and destroy all physical and electronic copies. Thank you.