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

Dne 7.9.2016 v 23:11 John Ament napsal(a): > That's kind of an odd response. > > > How does CDI-30 only work for request context? What makes you believe > that? @RequestScoped - makes sense @ApplicationScoped - is usually always active, no activation needed @SessionScoped - activate/deactivate is not enough, you have to associate the context with some storage @ConversationScoped - even more complicated, you need a storage and conversation ids > > > 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: >>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 >> > ------------------------------------------------------------------------ > 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. > > > _______________________________________________ > cdi-dev mailing list > cdi-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/cdi-dev > > Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 ( http://www.apache.org/licenses/LICENSE-2.0.html). For all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information. > -- Martin Kouba Software Engineer Red Hat, Czech Republic _______________________________________________ cdi-dev mailing list cdi-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/cdi-dev Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 ( http://www.apache.org/licenses/LICENSE-2.0.html). For all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.