March 2015 - cdi-dev - Jboss List Archives

[JBoss JIRA] (CDI-452) Specify that web scoped (request, session, application) beans are injectable in async servlets

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-452?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand commented on CDI-452: ------------------------------------------ I agree [~edburns], we really should revisit contexts to see how we could change API to be able to propagate them in asynchronous operation. > Specify that web scoped (request, session, application) beans are injectable in async servlets > ---------------------------------------------------------------------------------------------- > > Key: CDI-452 > URL: https://issues.jboss.org/browse/CDI-452 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Java EE integration > Affects Versions: 1.0 > Reporter: Ed Burns > Priority: Trivial > Fix For: 2.0 (discussion) > > > Consider this code based on this blog post: < https://weblogs.java.net/blog/swchan2/archive/2013/06/06/asynchronous-ser... >. > {code} > @WebServlet(urlPatterns="/test2", asyncSupported=true) > public class TestAsyncMESServlet extends HttpServlet { > @Resource > private ManagedExecutorService managedExecutorService; > @Inject > MyRunnableImpl myRunnableImpl; > @Override > protected void doGet(HttpServletRequest req, HttpServletResponse res) > throws ServletException, IOException { > final AsyncContext asyncContext = req.startAsync(); > final PrintWriter writer = res.getWriter(); > managedExecutorService.submit(myRunnableImpl); > } > public static class MyRunnableImpl implements Runnable { > @Inject > Bean bean; // Bean is @RequestScoped > @Override > public void run() { > writer.println("Done"); > asyncContext.complete(); > } > } > } > {code} > According to Jozef Hartzinger, this currently does not work, because only @Dependent and @ApplicationScoped beans are propagated to the new thread. To keep CDI relevant in light of the reactive programming movement and the popularity of node.js, we need to make this work. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (CDI-452) Specify that web scoped (request, session, application) beans are injectable in async servlets

by Antoine Sabot-Durand (JIRA)

[ https://issues.jboss.org/browse/CDI-452?page=com.atlassian.jira.plugin.sy... ] Antoine Sabot-Durand updated CDI-452: ------------------------------------- Fix Version/s: 2.0 (discussion) > Specify that web scoped (request, session, application) beans are injectable in async servlets > ---------------------------------------------------------------------------------------------- > > Key: CDI-452 > URL: https://issues.jboss.org/browse/CDI-452 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Java EE integration > Affects Versions: 1.0 > Reporter: Ed Burns > Priority: Trivial > Fix For: 2.0 (discussion) > > > Consider this code based on this blog post: < https://weblogs.java.net/blog/swchan2/archive/2013/06/06/asynchronous-ser... >. > {code} > @WebServlet(urlPatterns="/test2", asyncSupported=true) > public class TestAsyncMESServlet extends HttpServlet { > @Resource > private ManagedExecutorService managedExecutorService; > @Inject > MyRunnableImpl myRunnableImpl; > @Override > protected void doGet(HttpServletRequest req, HttpServletResponse res) > throws ServletException, IOException { > final AsyncContext asyncContext = req.startAsync(); > final PrintWriter writer = res.getWriter(); > managedExecutorService.submit(myRunnableImpl); > } > public static class MyRunnableImpl implements Runnable { > @Inject > Bean bean; // Bean is @RequestScoped > @Override > public void run() { > writer.println("Done"); > asyncContext.complete(); > } > } > } > {code} > According to Jozef Hartzinger, this currently does not work, because only @Dependent and @ApplicationScoped beans are propagated to the new thread. To keep CDI relevant in light of the reactive programming movement and the popularity of node.js, we need to make this work. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

Update on Async event doc

by Antoine Sabot-Durand

Hi all, I compiled all the feedback and decision we took regarding async events and updated the Google Doc : https://docs.google.com/document/d/1Tm_fZWS6569YqCH9lGxuqBGzS9gfupic-vv1d... <https://docs.google.com/document/d/1Tm_fZWS6569YqCH9lGxuqBGzS9gfupic-vv1d...> The following point stays open. I’d like to close them (if possible) during the next meeting on Tuesday 1) Async delivery mechanism (comment by Jozef) Should we write in the spec about how threads for events delivery should be used? Personally I’d rather not: I think this should be let to implementation, the specification should only describe the expected behavior (concurrency or not). now I may have missed something. 2) Exception Handling (comment by Jozef) I didn’t write anything about exception and we should decide what happens if an exception occurs in an observer during async event dispatch. I think that it shouldn’t impact other observers and that we should stick to the way CompletionStage API works today. 3) Async event activation on both ends We all agree that we need to explicitly fire event asynchronously on the producer side (fireAsync()). The discussion in 8.1 is about adding a way to accept async call on the consumer (observer) side. a) As events are often triggered in other parts of the application than the parts that consume them (most CDI framework lib fire events foe end user code) preventing user to decide if an observer can be called asynchronously could lead to issues and will prevent library developper to use fireAsync() (in a defensive coding approach). b) On the other hand, when placed in the same application, it’ll be very confusing for user to have to fireAsync() and enable async observer to activate this new feature. I propose an opt-out approach. We add ‘asyncSupported' member to ‘@Observes' annotation with ‘true’ as default value. So in case of b) the end user won’t have to explicitly activate async on observer and i case of a) user detecting issue coming from async treatment of an event can explicitly declares one or more observer not compatible with async resolution with @Observes(asyncSupported=False) 4) Support observer ordering with async events I think we should keep event ordering for synchronous event and ignore this feature in async event. I don’t see obvious use case to be async and ordered. 5) Context propagation I understand that propagating contexts in async event would impact easily context API. My only concern here is to be define async event to keep this feature possible. If I forgot points please comment this mail and the doc so we can take final decision during next meeting. Thank you Antoine

9 years, 9 months

3
5
0 / 0

Async event material

by Antoine Sabot-Durand

Hi all, For the info there are 2 docs (https://docs.google.com/document/d/1wJFvThqS8SrmKiuWsWgWH252k58PHGvM_iKeP... <https://docs.google.com/document/d/1wJFvThqS8SrmKiuWsWgWH252k58PHGvM_iKeP...> and https://docs.google.com/document/d/1Tm_fZWS6569YqCH9lGxuqBGzS9gfupic-vv1d... <https://docs.google.com/document/d/1Tm_fZWS6569YqCH9lGxuqBGzS9gfupic-vv1d...>) and a lot meeting transcript on the subject (http://transcripts.jboss.org/meeting/irc.freenode.org/cdi-dev/2015/index.... <http://transcripts.jboss.org/meeting/irc.freenode.org/cdi-dev/2015/index....>). I know it’s not fun to read all these (some info is outdated) but it’s a nice way to understand all the point we already discussed and avoid going back on them without a good reason. Yes, we spent a looooot of time on this async stuff but remember it’s the number 1 requested feature by our end user so we should really avoid f***ing it up. Antoine

9 years, 9 months

1
0
0 / 0

Invitation mise à jour: CDI weekly meeting - Toutes les semaines entre 18:00 et 19:00 le Mardi (ASD Perso)

by antoine＠sabot-durand.net

Cet événement a été modifié. Titre : CDI weekly meeting View your event at https://www.google.com/calendar/event?action=VIEW&eid=YmdhdXVtcDdnNjhlM3B.... View your event at https://www.google.com/calendar/event?action=VIEW&eid=YmdhdXVtcDdnNjhlM3B.... View your event at https://www.google.com/calendar/event?action=VIEW&eid=YmdhdXVtcDdnNjhlM3B.... Date : Toutes les semaines entre 18:00 et 19:00 le Mardi Paris (modifié) Lieu : IRC #cdi-dev channel on freenode Appel vidéo: https://plus.google.com/hangouts/_/sabot-durand.net/antoine-cdi <https://plus.google.com/hangouts/_/sabot-durand.net/antoine-cdi?hceid=YW5...> Agenda : ASD Perso Participants : * Antoine Sabot-Durand- organisateur * cdi-dev Détails de l'événement : https://www.google.com/calendar/event?action=VIEW&eid=XzcxMGpnZ3BrNjEwaml... Invitation de Google Agenda : https://www.google.com/calendar/ Vous recevez ce message à l'adresse cdi-dev(a)lists.jboss.org, car vous participez à cet événement. Pour ne plus recevoir de notifications pour cet événement à l'avenir, refusez cet événement. Vous avez également la possibilité de créer un compte Google sur la page https://www.google.com/calendar/ et de définir vous-même les paramètres de notification pour l'intégralité de votre agenda.

9 years, 9 months

1
0
0 / 0

Wrong google invitation.

by Antoine Sabot-Durand

Hi all, I send by mistake a false invitation for our meeting. It’s not on Wednesday but on Tuesday. Sorry for that Antoine

9 years, 9 months

2
1
0 / 0

Re: [cdi-dev] Invitation: CDI weekly meeting - Toutes les semaines entre

by Werner Keil

It's all French, but I suppose the meeting is today not tomorrow? As mentioned, I can't use IRC in the office, and there's an overlap with JSR 364 (phone call works as long as it's not an international line) so I won't be able to join this week I'm afraid. If Europe also gets to Daylight Saving, the other call may be later, then I could probably attend both (from home;-) Werner On Tue, Mar 17, 2015 at 4:06 PM, <cdi-dev-request(a)lists.jboss.org> wrote: > Send cdi-dev mailing list submissions to > cdi-dev(a)lists.jboss.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.jboss.org/mailman/listinfo/cdi-dev > or, via email, send a message with subject or body 'help' to > cdi-dev-request(a)lists.jboss.org > > You can reach the person managing the list at > cdi-dev-owner(a)lists.jboss.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of cdi-dev digest..." > > > Today's Topics: > > 1. Re: CDI SE Google Doc Updated (Martin Kouba) > 2. Invitation: CDI weekly meeting - Toutes les semaines entre > 18:00 et 19:00 le Mercredi (ASD Perso) (Antoine Sabot-Durand) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 17 Mar 2015 13:05:40 +0100 > From: Martin Kouba <mkouba(a)redhat.com> > Subject: Re: [cdi-dev] CDI SE Google Doc Updated > To: "John D. Ament" <john.d.ament(a)gmail.com>, Jozef Hartinger > <jharting(a)redhat.com>, Antoine Sabot-Durand < > antoine(a)sabot-durand.net> > Cc: "cdi-dev(a)lists.jboss.org" <cdi-dev(a)lists.jboss.org> > Message-ID: <55081894.8050104(a)redhat.com> > Content-Type: text/plain; charset=utf-8; format=flowed > > Dne 17.3.2015 v 10:49 John D. Ament napsal(a): > > > > > > On Tue, Mar 17, 2015 at 4:50 AM Martin Kouba <mkouba(a)redhat.com > > <mailto:mkouba@redhat.com>> wrote: > > > > It's ok to have the same default bean discovery mode in Java SE. > > However, I think there is no easy way to scan the classpath and > "detect" > > bean archives without beans.xml, i.e. implicit bean archives without > the > > descriptor. > > > > > > You should be able to read java.class.path to determine the possible > > archives. Then use the URL of the class itself to find which JAR it > > came from. > > I'm not sure this will cover all use-cases (Web Start, extension > classes, ...). Moreover, elements of the class are platform-specific. So > it wouldn't be trivial to parse it. > > > > > > > That's the reason why bean archives without beans.xml are not > supported > > in Weld SE. > > > > If anyone knows how to implement this properly, speak out. > > > > Martin > > > > Dne 17.3.2015 v 07:22 Jozef Hartinger napsal(a): > > > > > > On 03/16/2015 05:45 PM, Antoine Sabot-Durand wrote: > > >> > > >>> Le 16 mars 2015 ? 11:02, Jozef Hartinger <jharting(a)redhat.com > > <mailto:jharting@redhat.com> > > >>> <mailto:jharting@redhat.com <mailto:jharting@redhat.com>>> a > > ?crit : > > >>> > > >>> Btw was there any further discussion about the bean discovery > > mode in SE > > >>> > > >> > > >> For the time being we decided to have the same discovery mode in > SE > > >> (default to Annotated). If someone has a good reason to change > the > > >> default mode in SE and/or add a new discovery mode, I?d be glad > to > > >> hear about it. > > > > > http://lists.jboss.org/__pipermail/cdi-dev/2015-March/__006334.html > > <http://lists.jboss.org/pipermail/cdi-dev/2015-March/006334.html> > > >> > > >> > > >>> On 03/16/2015 10:45 AM, Jozef Hartinger wrote: > > >>>> The CDIProvider serves as a kind of SPI for CDI's static > > methods to > > >>>> be able to call into the implementation. I don't think reusing > it > > >>>> also as a user-facing code is a good idea. What people > > suggesting to > > >>>> reuse CDIProvider had in mind, I think, was to reuse it as the > SPI > > >>>> for talking to the CDI implementation instead. That way, the > > >>>> initialize() static method of > > CDIContainer/StartedCDI/__whatever we > > >>>> call it can use CDIProvider internally to actually start the > > container. > > >>>> > > >>>> In addition, the current proposal does not make it possible to > > >>>> implement parallel container instances. > > >>>> > > >>>> Jozef > > >>>> > > >>>> On 03/15/2015 05:03 PM, John D. Ament wrote: > > >>>>> HI all, > > >>>>> > > >>>>> Apologies for being a week late on getting this doc > together. I > > >>>>> had some personal issues pop up after my leg came out of its > cast > > >>>>> that consumed most of my week last week. > > >>>>> > > >>>>> Anywho, I've updated the doc with a summary of what was > discussed > > >>>>> with CDI SE bootstrap support. You can find that here: > > >>>>> > > > https://docs.google.com/__document/d/1LgsGT-__AAlrF72Z5pW4xNQiVjUHGUME46Z... > > < > https://docs.google.com/document/d/1LgsGT-AAlrF72Z5pW4xNQiVjUHGUME46ZmB-w... > > > > >>>>> > > >>>>> There are two minor changes that I made from where we last > > >>>>> discussed, as when I was putting together code I found some > gaps > > >>>>> and figured it best to fix them here than later. > > >>>>> > > >>>>> 1. CDIProvider does not implement AutoCloseable. Since CDI > class > > >>>>> maintains a reference to the provider, implementing > AutoCloseable > > >>>>> was not adding anything. > > >>>>> > > >>>>> 2. I added a method boolean isInitialized() so that the > > caller can > > >>>>> know if they need to start the container (or if it's already > > running). > > >>>>> > > >>>>> Locally, I've also modified the CDI.current() method to use > > >>>>> getCDIProvider() instead of internally finding the provider > since > > >>>>> we now have a getter. > > >>>>> > > >>>>> One thing I'd like to get feedback on is if calling > > >>>>> initialize/shutdown in a container should throw > > >>>>> IllegalStateException, or probably better to throw > > >>>>> UnsupportedOperationException when called in EE containers. > > >>>>> > > >>>>> Let me know your thoughts. > > >>>>> > > >>>>> John > > >>>>> > > >>>>> > > >>>>> > > >>>>> _________________________________________________ > > >>>>> cdi-dev mailing list > > >>>>> cdi-dev(a)lists.jboss.org <mailto:cdi-dev@lists.jboss.org> > > >>>>> https://lists.jboss.org/__mailman/listinfo/cdi-dev > > <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 > > <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. > > >>>> > > >>>> > > >>>> > > >>>> _________________________________________________ > > >>>> cdi-dev mailing list > > >>>> cdi-dev(a)lists.jboss.org <mailto:cdi-dev@lists.jboss.org> > > >>>> https://lists.jboss.org/__mailman/listinfo/cdi-dev > > <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 > > <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. > > >>> > > >>> _________________________________________________ > > >>> cdi-dev mailing list > > >>> cdi-dev(a)lists.jboss.org <mailto:cdi-dev@lists.jboss.org> > > <mailto:cdi-dev@lists.jboss.__org <mailto:cdi-dev@lists.jboss.org>> > > >>> https://lists.jboss.org/__mailman/listinfo/cdi-dev > > <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 > > <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. > > >> > > > > > > > > > > > > _________________________________________________ > > > cdi-dev mailing list > > > cdi-dev(a)lists.jboss.org <mailto:cdi-dev@lists.jboss.org> > > > https://lists.jboss.org/__mailman/listinfo/cdi-dev > > <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 > > <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. > > > > > _________________________________________________ > > cdi-dev mailing list > > cdi-dev(a)lists.jboss.org <mailto:cdi-dev@lists.jboss.org> > > https://lists.jboss.org/__mailman/listinfo/cdi-dev > > <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 > > <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. > > > > > > ------------------------------ > > Message: 2 > Date: Tue, 17 Mar 2015 15:06:12 +0000 > From: Antoine Sabot-Durand <antoine(a)sabot-durand.net> > Subject: [cdi-dev] Invitation: CDI weekly meeting - Toutes les > semaines entre 18:00 et 19:00 le Mercredi (ASD Perso) > To: cdi-dev <cdi-dev(a)lists.jboss.org> > Message-ID: <001a11c3ca14af712a05117d4e78(a)google.com> > Content-Type: text/plain; charset="iso-8859-1" > > Vous avez ?t? invit? ? l'?v?nement suivant. > > Titre : CDI weekly meeting > View your event at > > https://www.google.com/calendar/event?action=VIEW&eid=YmdhdXVtcDdnNjhlM3B... > . > View your event at > > https://www.google.com/calendar/event?action=VIEW&eid=YmdhdXVtcDdnNjhlM3B... > . > View your event at > > https://www.google.com/calendar/event?action=VIEW&eid=YmdhdXVtcDdnNjhlM3B.... > Date?: Toutes les semaines entre 18:00 et 19:00 le Mercredi Paris > Lieu : IRC #cdi-dev channel on freenode > Appel vid?o: > https://plus.google.com/hangouts/_/sabot-durand.net/antoine-cdi > < > https://plus.google.com/hangouts/_/sabot-durand.net/antoine-cdi?hceid=YW5... > > > Agenda?: ASD Perso > Participants?: > * Antoine Sabot-Durand- organisateur > * cdi-dev > > D?tails de l'?v?nement : > > https://www.google.com/calendar/event?action=VIEW&eid=XzcxMGpnZ3BrNjEwaml... > > Invitation de Google?Agenda?: https://www.google.com/calendar/ > > Vous recevez ce message ? l'adresse cdi-dev(a)lists.jboss.org, car vous > participez ? cet ?v?nement. > > Pour ne plus recevoir de notifications pour cet ?v?nement ? l'avenir, > refusez cet ?v?nement. Vous avez ?galement la possibilit? de cr?er un > compte Google sur la page https://www.google.com/calendar/ et de d?finir > vous-m?me les param?tres de notification pour l'int?gralit? de votre > agenda. > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > http://lists.jboss.org/pipermail/cdi-dev/attachments/20150317/9b6900bb/at... > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: not available > Type: text/calendar > Size: 2356 bytes > Desc: not available > Url : > http://lists.jboss.org/pipermail/cdi-dev/attachments/20150317/9b6900bb/at... > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: invite.ics > Type: application/ics > Size: 2413 bytes > Desc: not available > Url : > http://lists.jboss.org/pipermail/cdi-dev/attachments/20150317/9b6900bb/at... > > ------------------------------ > > _______________________________________________ > 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. > > End of cdi-dev Digest, Vol 52, Issue 53 > *************************************** >

9 years, 9 months

1
0
0 / 0

Invitation: CDI weekly meeting - Toutes les semaines entre 18:00 et 19:00 le Mercredi (ASD Perso)

by Antoine Sabot-Durand

Vous avez été invité à l'événement suivant. Titre : CDI weekly meeting View your event at https://www.google.com/calendar/event?action=VIEW&eid=YmdhdXVtcDdnNjhlM3B.... View your event at https://www.google.com/calendar/event?action=VIEW&eid=YmdhdXVtcDdnNjhlM3B.... View your event at https://www.google.com/calendar/event?action=VIEW&eid=YmdhdXVtcDdnNjhlM3B.... Date : Toutes les semaines entre 18:00 et 19:00 le Mercredi Paris Lieu : IRC #cdi-dev channel on freenode Appel vidéo: https://plus.google.com/hangouts/_/sabot-durand.net/antoine-cdi <https://plus.google.com/hangouts/_/sabot-durand.net/antoine-cdi?hceid=YW5...> Agenda : ASD Perso Participants : * Antoine Sabot-Durand- organisateur * cdi-dev Détails de l'événement : https://www.google.com/calendar/event?action=VIEW&eid=XzcxMGpnZ3BrNjEwaml... Invitation de Google Agenda : https://www.google.com/calendar/ Vous recevez ce message à l'adresse cdi-dev(a)lists.jboss.org, car vous participez à cet événement. Pour ne plus recevoir de notifications pour cet événement à l'avenir, refusez cet événement. Vous avez également la possibilité de créer un compte Google sur la page https://www.google.com/calendar/ et de définir vous-même les paramètres de notification pour l'intégralité de votre agenda.

9 years, 9 months

1
0
0 / 0

CDI SE Google Doc Updated

by John D. Ament

HI all, Apologies for being a week late on getting this doc together. I had some personal issues pop up after my leg came out of its cast that consumed most of my week last week. Anywho, I've updated the doc with a summary of what was discussed with CDI SE bootstrap support. You can find that here: https://docs.google.com/document/d/1LgsGT-AAlrF72Z5pW4xNQiVjUHGUME46ZmB-w... There are two minor changes that I made from where we last discussed, as when I was putting together code I found some gaps and figured it best to fix them here than later. 1. CDIProvider does not implement AutoCloseable. Since CDI class maintains a reference to the provider, implementing AutoCloseable was not adding anything. 2. I added a method boolean isInitialized() so that the caller can know if they need to start the container (or if it's already running). Locally, I've also modified the CDI.current() method to use getCDIProvider() instead of internally finding the provider since we now have a getter. One thing I'd like to get feedback on is if calling initialize/shutdown in a container should throw IllegalStateException, or probably better to throw UnsupportedOperationException when called in EE containers. Let me know your thoughts. John

9 years, 9 months

4
10
0 / 0

[JBoss JIRA] (CDI-26) Bootstrap API for CDI

by Jozef Hartinger (JIRA)

[ https://issues.jboss.org/browse/CDI-26?page=com.atlassian.jira.plugin.sys... ] Jozef Hartinger commented on CDI-26: ------------------------------------ An alternative proposal that does not prevent parallel container instances: {code:java} public abstract class ControlledCDI<T> extends CDI<T> implements AutoCloseable { public static ControlledCDI<Object> initialize() { // TODO: Use CDIProvider internally to talk to the impl } public static ControlledCDI<Object> initialize(Map<String, Object> properties) { // TODO: Use CDIProvider internally to talk to the impl } public abstract void close(); } {code} Usage: {code:java} try (ControlledCDI<Object> cdi = ControlledCDI.initialize()) { Foo foo = cdi.select(Foo.class).get(); System.out.println(foo.computeResult()); } {code} Note that this is a preliminary proposal. The class name is subject to change plus we'll most likely need a builder API instead of the static methods in the end. > Bootstrap API for CDI > --------------------- > > Key: CDI-26 > URL: https://issues.jboss.org/browse/CDI-26 > Project: CDI Specification Issues > Issue Type: Feature Request > Components: Packaging and Deployment > Affects Versions: 1.0, 1.1.PFD, 1.2.Final > Reporter: Pete Muir > Fix For: 2.0 (discussion) > > > Weld and other CDI impls allow an embedded mode. > See http://docs.jboss.org/weld/reference/latest/en-US/html/environments.html#... for example -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

cdi-dev March 2015