Re: [cdi-dev] cdi-dev Digest, Vol 46, Issue 1
by Werner Keil
Hi,
Is the call taking place today?
I seem to be the only one in the Hangout[?]
IRC also gives troubles, the #cdi-dev room does not let me in for now. Is
there any credential or user name you need to know to let us join?
Thanks,
Werner
On Mon, Sep 1, 2014 at 3:24 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. Invitation: CDI meeting @ Wed 3 Sep 2014 18:00 - 19:00 (ASD
> Perso) (Antoine Sabot-Durand)
> 2. [JBoss JIRA] (CDI-45) Optional Injection Points
> (Antoine Sabot-Durand (JIRA))
> 3. Re: Spec launch meeting and CDI weekly meeting (Filipe Portes)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 01 Sep 2014 09:47:52 +0000
> From: Antoine Sabot-Durand <antoine(a)sabot-durand.net>
> Subject: [cdi-dev] Invitation: CDI meeting @ Wed 3 Sep 2014 18:00 -
> 19:00 (ASD Perso)
> To: "cdi-dev(a)lists.jboss.org" <cdi-dev(a)lists.jboss.org>
> Message-ID: <001a11c38b1c7c974f0501fde5be(a)google.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> You have been invited to the following event.
>
> Title: CDI meeting
> When: Wed 3 Sep 2014 18:00 - 19:00 Paris
> Where: #cdi-dev on freenode IRC
> Video call: https://plus.google.com/hangouts/_/sabot-durand.net/antoine
> <
> https://plus.google.com/hangouts/_/sabot-durand.net/antoine?hceid=YW50b2l...
> >
> Calendar: ASD Perso
> Who:
> * Antoine Sabot-Durand- organiser
> * cdi-dev(a)lists.jboss.org
>
> Event details:
>
> https://www.google.com/calendar/event?action=VIEW&eid=ampuMWI2amVjbjIxa2I...
>
> Invitation from Google Calendar: https://www.google.com/calendar/
>
> You are receiving this courtesy email at the account
> cdi-dev(a)lists.jboss.org because you are an attendee of this event.
>
> To stop receiving future notifications for this event, decline this event.
> Alternatively, you can sign up for a Google account at
> https://www.google.com/calendar/ and control your notification settings
> for
> your entire calendar.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://lists.jboss.org/pipermail/cdi-dev/attachments/20140901/4f2d5560/at...
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: text/calendar
> Size: 1074 bytes
> Desc: not available
> Url :
> http://lists.jboss.org/pipermail/cdi-dev/attachments/20140901/4f2d5560/at...
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: invite.ics
> Type: application/ics
> Size: 1102 bytes
> Desc: not available
> Url :
> http://lists.jboss.org/pipermail/cdi-dev/attachments/20140901/4f2d5560/at...
>
> ------------------------------
>
> Message: 2
> Date: Mon, 1 Sep 2014 05:55:00 -0400 (EDT)
> From: "Antoine Sabot-Durand (JIRA)" <issues(a)jboss.org>
> Subject: [cdi-dev] [JBoss JIRA] (CDI-45) Optional Injection Points
> To: cdi-dev(a)lists.jboss.org
> Message-ID:
> <JIRA.12428685.1295838622000.20248.1409565300619(a)Atlassian.JIRA>
> Content-Type: text/plain; charset=UTF-8
>
>
> [
> https://issues.jboss.org/browse/CDI-45?page=com.atlassian.jira.plugin.sys...
> ]
>
> Antoine Sabot-Durand updated CDI-45:
> ------------------------------------
> Fix Version/s: 2.0 (discussion)
> (was: TBD)
>
>
> > Optional Injection Points
> > -------------------------
> >
> > Key: CDI-45
> > URL: https://issues.jboss.org/browse/CDI-45
> > Project: CDI Specification Issues
> > Issue Type: Feature Request
> > Components: Resolution
> > Affects Versions: 1.0
> > Reporter: Stuart Douglas
> > Fix For: 2.0 (discussion)
> >
> >
> > There are occoasions where it may be useful for some injection points to
> be optional, e.g.
> > @Inject
> > @Optional
> > MyBean bean;
> > This would behave the same as a normal injection point, however it will
> not cause the deployment to fail if it is not satisified.
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.3.1#6329)
>
>
> ------------------------------
>
> Message: 3
> Date: Mon, 1 Sep 2014 10:24:37 -0300
> From: Filipe Portes <omeuefilipe(a)gmail.com>
> Subject: Re: [cdi-dev] Spec launch meeting and CDI weekly meeting
> To: Mark Paluch <mpaluch(a)paluch.biz>
> Cc: cdi-dev <cdi-dev(a)lists.jboss.org>
> Message-ID:
> <CAKwwkgQHmM0Gvr=hW=GdU65bfGY+2Z4-PWpRp0Fqu=
> Xhv_hngQ(a)mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> here in brazil 16:00 UTC equals to 1:00 pm, so it's pretty good.
>
>
> On Sat, Aug 30, 2014 at 9:00 AM, Mark Paluch <mpaluch(a)paluch.biz> wrote:
>
> > Either way is fine with me. In general 16:00 UTC is a good choice since
> it
> > seems not to be mid-might for anyone that is involved.
> >
> > Best regards, Mark
> >
> > Am 30.08.2014 um 12:53 schrieb Thorben Janssen <thjanssen123(a)gmail.com>:
> >
> > Wednesday at the same time is fine for me.
> > Do you want to shift all meetings or only this one?
> >
> > Regards,
> > Thorben
> > ------------------------------
> > Von: Antoine Sabot-Durand <antoine(a)sabot-durand.net>
> > Gesendet: ?30.?08.?2014 12:18
> > An: John D. Ament <john.d.ament(a)gmail.com>
> > Cc: cdi-dev <cdi-dev(a)lists.jboss.org>
> > Betreff: Re: [cdi-dev] Spec launch meeting and CDI weekly meeting
> >
> > Hi John,
> >
> > Sorry to have missed that. According to Pete, French are holidays
> > specialists. I guess I have to improve my expertise in this domain ;).
> >
> > Is it ok for everybody to switch the meeting on Wednesday at the same
> > time ? If there ware no objection I will send you an invitation Monday.
> >
> >
> >
> > Antoine
> >
> > Le 29 ao?t 2014 ? 18:53, John D. Ament <john.d.ament(a)gmail.com> a
> ?crit :
> >
> > Could it be pushed to later in the week? Monday's a holiday in the US.
> >
> >
> > On Fri, Aug 29, 2014 at 9:32 AM, Antoine Sabot-Durand <
> > antoine(a)sabot-durand.net> wrote:
> >
> >> Hi All,
> >>
> >> On CDI 1.1, we use to have a weekly meeting each monday at 16:00 UTC
> >> (that?s 9:00 am PDT, 6:00 pm CEST and 9:30 pm IST). It?s hard to find a
> >> time slot that please everybody (from US West Coast to India), so Ir
> >> propose we keep this track. Now, if you have issue with this slot (if
> you
> >> live in New Zealand or Australia) say it and we?ll try to figure out a
> >> better slot (even if there?s no ideal one).
> >>
> >> The meeting place is the IRC channel and last one hour. We use an IRC
> bot
> >> (jbott) to keep track of meeting minutes for the record or people
> unable to
> >> attend the meeting. You can get familiarised with BOT commands here :
> >> https://wiki.debian.org/MeetBot
> >>
> >> So I propose we have our JSR launch meeting next monday (sept 1st) with
> >> the following agenda :
> >>
> >> - Discussion on the working method and tools used (mainly do we use
> >> Google Drive or Github with Asciidoc for working doc)
> >> - Discussion on each workshop I mentioned in my previous post and
> missing
> >> workshop
> >> * Workshop teams
> >> * Workflow chosen
> >> * estimated deadline (hard to say since we don?t know our workforce, but
> >> will be refined later)
> >> - Q & A if we still have time
> >>
> >> Note that It think we should avoid talking about specific content of
> >> workshop except if you think things are missing or that we could forgot
> >> them.
> >> If you want to see other points in the agenda let me know.
> >>
> >> I?m thrilled to start this great project with you guys.
> >>
> >> Antoine
> >>
> >> _______________________________________________
> >> 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.
> >>
> >
> >
> > _______________________________________________
> > 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.
> >
> >
> >
> > _______________________________________________
> > 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.
> >
>
>
>
> --
> Filipe Portes - @filipeportes
> Senior Java EE/Web
> JUGLeader Gojava <http://www.gojava.org/> - @gojava
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://lists.jboss.org/pipermail/cdi-dev/attachments/20140901/57990ba6/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 46, Issue 1
> **************************************
>
9 years, 8 months
Spec launch meeting and CDI weekly meeting
by Antoine Sabot-Durand
Hi All,
On CDI 1.1, we use to have a weekly meeting each monday at 16:00 UTC (that’s 9:00 am PDT, 6:00 pm CEST and 9:30 pm IST). It’s hard to find a time slot that please everybody (from US West Coast to India), so Ir propose we keep this track. Now, if you have issue with this slot (if you live in New Zealand or Australia) say it and we’ll try to figure out a better slot (even if there’s no ideal one).
The meeting place is the IRC channel and last one hour. We use an IRC bot (jbott) to keep track of meeting minutes for the record or people unable to attend the meeting. You can get familiarised with BOT commands here :
https://wiki.debian.org/MeetBot <https://wiki.debian.org/MeetBot>
So I propose we have our JSR launch meeting next monday (sept 1st) with the following agenda :
- Discussion on the working method and tools used (mainly do we use Google Drive or Github with Asciidoc for working doc)
- Discussion on each workshop I mentioned in my previous post and missing workshop
* Workshop teams
* Workflow chosen
* estimated deadline (hard to say since we don’t know our workforce, but will be refined later)
- Q & A if we still have time
Note that It think we should avoid talking about specific content of workshop except if you think things are missing or that we could forgot them.
If you want to see other points in the agenda let me know.
I’m thrilled to start this great project with you guys.
Antoine
9 years, 8 months
[JBoss JIRA] (CDI-45) Optional Injection Points
by Antonin Stefanutti (JIRA)
[ https://issues.jboss.org/browse/CDI-45?page=com.atlassian.jira.plugin.sys... ]
Antonin Stefanutti edited comment on CDI-45 at 9/1/14 5:14 PM:
---------------------------------------------------------------
Then one potential compromise would be to enrich the existing abstractions, either {{Instance}} or {{Provider}} with the equivalent semantic that of {{Optional}}. For example:
{code}
@Inject
Provider<MyBean> bean;
if (bean.isPresent())
bean.get();
{code}
Or if we think {{Optional}} is a convenient abstraction:
{code}
@Inject
Provider<MyBean> bean;
bean.getOptional();
{code}
In any case, I think that a {{isSatisfied()}} / {{isResolvable()}} method is missing on the {{Instance}} interface when alternatives are enabled for example and that would avoid writing {{!isUnsatisfied() && !isAmbiguous()}}.
As per backward compatibility for these interfaces, are they really meant to be implemented aside from the implementations? That would avoid introducing another interface. If not maybe default method in Java 8 could help.
was (Author: stefanutti):
Then one potential compromise would be to enrich the existing abstractions, either {{Instance}} or {{Provider}} with the equivalent semantic that of {{Optional}}. For example:
{code}
@Inject
Provider<MyBean> bean;
if (bean.isPresent())
bean.get();
{code}
In any case, I think that a {{isSatisfied()}} / {{isResolvable()}} method is missing on the {{Instance}} interface when alternatives are enabled for example and that would avoid writing {{!isUnsatisfied() && !isAmbiguous()}}.
As per backward compatibility for these interfaces, are they really meant to be implemented aside from the implementations? That would avoid introducing another interface. If not maybe default method in Java 8 could help.
> Optional Injection Points
> -------------------------
>
> Key: CDI-45
> URL: https://issues.jboss.org/browse/CDI-45
> Project: CDI Specification Issues
> Issue Type: Feature Request
> Components: Resolution
> Affects Versions: 1.0
> Reporter: Stuart Douglas
> Fix For: 2.0 (discussion)
>
>
> There are occoasions where it may be useful for some injection points to be optional, e.g.
> @Inject
> @Optional
> MyBean bean;
> This would behave the same as a normal injection point, however it will not cause the deployment to fail if it is not satisified.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 8 months
[JBoss JIRA] (CDI-45) Optional Injection Points
by Antonin Stefanutti (JIRA)
[ https://issues.jboss.org/browse/CDI-45?page=com.atlassian.jira.plugin.sys... ]
Antonin Stefanutti edited comment on CDI-45 at 9/1/14 3:43 PM:
---------------------------------------------------------------
Then one potential compromise would be to enrich the existing abstractions, either {{Instance}} or {{Provider}} with the equivalent semantic that of {{Optional}}. For example:
{code}
@Inject
Provider<MyBean> bean;
if (bean.isPresent())
bean.get();
{code}
In any case, I think that a {{isSatisfied()}} / {{isResolvable()}} method is missing on the {{Instance}} interface when alternatives are enabled for example and that would avoid writing {{!isUnsatisfied() && !isAmbiguous()}}.
As per backward compatibility for these interfaces, are they really meant to be implemented aside from the implementations? That would avoid introducing another interface. If not maybe default method in Java 8 could help.
was (Author: stefanutti):
Then one potential compromise would be to enrich the existing abstractions, either {{Instance}} or {{Provider}} with the {{Optional}} semantic. For example:
{code}
@Inject
Provider<MyBean> bean;
if (bean.isPresent())
bean.get();
{code}
In any case, I think that a {{isSatisfied()}} / {{isResolvable()}} method is missing on the {{Instance}} interface when alternatives are enabled for example and that would avoid writing {{!isUnsatisfied() && !isAmbiguous()}}.
As per backward compatibility for these interfaces, are they really meant to be implemented aside from the implementations? That would avoid introducing another interface. If not maybe default method in Java 8 could help.
> Optional Injection Points
> -------------------------
>
> Key: CDI-45
> URL: https://issues.jboss.org/browse/CDI-45
> Project: CDI Specification Issues
> Issue Type: Feature Request
> Components: Resolution
> Affects Versions: 1.0
> Reporter: Stuart Douglas
> Fix For: 2.0 (discussion)
>
>
> There are occoasions where it may be useful for some injection points to be optional, e.g.
> @Inject
> @Optional
> MyBean bean;
> This would behave the same as a normal injection point, however it will not cause the deployment to fail if it is not satisified.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 8 months
[JBoss JIRA] (CDI-45) Optional Injection Points
by Antonin Stefanutti (JIRA)
[ https://issues.jboss.org/browse/CDI-45?page=com.atlassian.jira.plugin.sys... ]
Antonin Stefanutti commented on CDI-45:
---------------------------------------
Then one potential compromise would be to enrich the existing abstractions, either {{Instance}} or {{Provider}} with the {{Optional}} semantic. For example:
{code}
@Inject
Provider<MyBean> bean;
if (bean.isPresent())
bean.get();
{code}
In any case, I think that a {{isSatisfied()}} / {{isResolvable()}} method is missing on the {{Instance}} interface when alternatives are enabled for example and that would avoid writing {{!isUnsatisfied() && !isAmbiguous()}}.
As per backward compatibility for these interfaces, are they really meant to be implemented aside from the implementations? That would avoid introducing another interface. If not maybe default method in Java 8 could help.
> Optional Injection Points
> -------------------------
>
> Key: CDI-45
> URL: https://issues.jboss.org/browse/CDI-45
> Project: CDI Specification Issues
> Issue Type: Feature Request
> Components: Resolution
> Affects Versions: 1.0
> Reporter: Stuart Douglas
> Fix For: 2.0 (discussion)
>
>
> There are occoasions where it may be useful for some injection points to be optional, e.g.
> @Inject
> @Optional
> MyBean bean;
> This would behave the same as a normal injection point, however it will not cause the deployment to fail if it is not satisified.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 8 months
[JBoss JIRA] (CDI-45) Optional Injection Points
by Romain Manni-Bucau (JIRA)
[ https://issues.jboss.org/browse/CDI-45?page=com.atlassian.jira.plugin.sys... ]
Romain Manni-Bucau commented on CDI-45:
---------------------------------------
sure, IMHO optional injection points have the exact same constraints as normal injection excepted it can be null
> Optional Injection Points
> -------------------------
>
> Key: CDI-45
> URL: https://issues.jboss.org/browse/CDI-45
> Project: CDI Specification Issues
> Issue Type: Feature Request
> Components: Resolution
> Affects Versions: 1.0
> Reporter: Stuart Douglas
> Fix For: 2.0 (discussion)
>
>
> There are occoasions where it may be useful for some injection points to be optional, e.g.
> @Inject
> @Optional
> MyBean bean;
> This would behave the same as a normal injection point, however it will not cause the deployment to fail if it is not satisified.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 8 months
[JBoss JIRA] (CDI-45) Optional Injection Points
by Renat Valeev (JIRA)
[ https://issues.jboss.org/browse/CDI-45?page=com.atlassian.jira.plugin.sys... ]
Renat Valeev commented on CDI-45:
---------------------------------
I think there could be an interface between Provider<T> and Instance<T>, which will have method isUnsatisfied(). So that way backward compatibility will be preserved.
The question is not only of how we declare, but also if the dependecy is ambiguous, should resolution fail for "optional" dependecy?
> Optional Injection Points
> -------------------------
>
> Key: CDI-45
> URL: https://issues.jboss.org/browse/CDI-45
> Project: CDI Specification Issues
> Issue Type: Feature Request
> Components: Resolution
> Affects Versions: 1.0
> Reporter: Stuart Douglas
> Fix For: 2.0 (discussion)
>
>
> There are occoasions where it may be useful for some injection points to be optional, e.g.
> @Inject
> @Optional
> MyBean bean;
> This would behave the same as a normal injection point, however it will not cause the deployment to fail if it is not satisified.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 8 months
[JBoss JIRA] (CDI-45) Optional Injection Points
by Romain Manni-Bucau (JIRA)
[ https://issues.jboss.org/browse/CDI-45?page=com.atlassian.jira.plugin.sys... ]
Romain Manni-Bucau commented on CDI-45:
---------------------------------------
Well Instance almost matches this need. Only known issue it has is the fact it doesn't only have isSatisfied(), get() methods so resolution is almost everytimes done lazily which is/can be slow compared to normal injection. Having SingletonInstance with only these methods (and Instance inheriting from it) could solve it but not sure this change can be introduced.
> Optional Injection Points
> -------------------------
>
> Key: CDI-45
> URL: https://issues.jboss.org/browse/CDI-45
> Project: CDI Specification Issues
> Issue Type: Feature Request
> Components: Resolution
> Affects Versions: 1.0
> Reporter: Stuart Douglas
> Fix For: 2.0 (discussion)
>
>
> There are occoasions where it may be useful for some injection points to be optional, e.g.
> @Inject
> @Optional
> MyBean bean;
> This would behave the same as a normal injection point, however it will not cause the deployment to fail if it is not satisified.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 8 months
[JBoss JIRA] (CDI-45) Optional Injection Points
by Renat Valeev (JIRA)
[ https://issues.jboss.org/browse/CDI-45?page=com.atlassian.jira.plugin.sys... ]
Renat Valeev commented on CDI-45:
---------------------------------
Have not spot that Optional is a class. But approach with @Optional or @Inject(optional=true) will mean that object can be null, which is not good.
> Optional Injection Points
> -------------------------
>
> Key: CDI-45
> URL: https://issues.jboss.org/browse/CDI-45
> Project: CDI Specification Issues
> Issue Type: Feature Request
> Components: Resolution
> Affects Versions: 1.0
> Reporter: Stuart Douglas
> Fix For: 2.0 (discussion)
>
>
> There are occoasions where it may be useful for some injection points to be optional, e.g.
> @Inject
> @Optional
> MyBean bean;
> This would behave the same as a normal injection point, however it will not cause the deployment to fail if it is not satisified.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 8 months
[JBoss JIRA] (CDI-45) Optional Injection Points
by Romain Manni-Bucau (JIRA)
[ https://issues.jboss.org/browse/CDI-45?page=com.atlassian.jira.plugin.sys... ]
Romain Manni-Bucau commented on CDI-45:
---------------------------------------
{code}
class InstanceImpl<T> implements Instance<T>, Serializable
{code}
that's rely on CDI implementation, Optional can't since the impl is in the JVM
> Optional Injection Points
> -------------------------
>
> Key: CDI-45
> URL: https://issues.jboss.org/browse/CDI-45
> Project: CDI Specification Issues
> Issue Type: Feature Request
> Components: Resolution
> Affects Versions: 1.0
> Reporter: Stuart Douglas
> Fix For: 2.0 (discussion)
>
>
> There are occoasions where it may be useful for some injection points to be optional, e.g.
> @Inject
> @Optional
> MyBean bean;
> This would behave the same as a normal injection point, however it will not cause the deployment to fail if it is not satisified.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
9 years, 8 months