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
10 years, 3 months
Re: [cdi-dev] Spec launch meeting and CDI weekly meeting
by Thorben Janssen
Wednesday at the same time is fine for me.
Do you want to shift all meetings or only this one?
Regards,
Thorben
----- Ursprüngliche Nachricht -----
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.
10 years, 3 months
Re: [cdi-dev] cdi-dev Digest, Vol 45, Issue 17
by Werner Keil
Antoine/all,
Happy to join the session, I am rather flexible between now and JavaOne
regarding days (there are JSR 362/4 calls on Tue and often IP WG calls on
Fri) or times.
It would be better on the long run if it is not too early in the day, as I
cannot say, if all projects or clients I work with allow IRC access through
the firewall. If I am in my own place, that and even Hangout, etc. is OK.
I submitted the form to join the EG. Exhibit B should be no problem, I have
a "rubber-stamping" GIMP file for that as a template while trying to help
make that easier down the road through JSR 364 and JCP.next;-)
Regards,
Werner
On Fri, Aug 29, 2014 at 9:36 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: Spec launch meeting and CDI weekly meeting (John D. Ament)
> 2. Re: Introduce myself (Thorben Janssen)
> 3. Re: EG membership status (Thorben Janssen)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 29 Aug 2014 12:53:10 -0400
> From: "John D. Ament" <john.d.ament(a)gmail.com>
> Subject: Re: [cdi-dev] Spec launch meeting and CDI weekly meeting
> To: Antoine Sabot-Durand <antoine(a)sabot-durand.net>
> Cc: cdi-dev <cdi-dev(a)lists.jboss.org>
> Message-ID:
> <
> CAOqetn_qPbZFExnhP0MZ1DTMYYmc52yz7rjCLSDYzN_b_R+Kdg(a)mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> 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.
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://lists.jboss.org/pipermail/cdi-dev/attachments/20140829/34b786a2/at...
>
> ------------------------------
>
> Message: 2
> Date: Fri, 29 Aug 2014 21:17:09 +0200
> From: Thorben Janssen <thjanssen123(a)gmail.com>
> Subject: Re: [cdi-dev] Introduce myself
> To: cdi-dev <cdi-dev(a)lists.jboss.org>
> Message-ID:
> <
> CAE9nDy9m-euJ7DoiyS9_KD3JXXF10Jv9Z1pRqVH1OcTzYkE+aA(a)mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hey everyone,
>
> I would also like to introduce myself. My name is Thorben Janssen and I
> live in Dresden, Germany.
> I have no experience with JCP or as an EG member but I am working with Java
> EE for more than 10 years. After some discussions with Antoine, I decided
> that it's time for a next step and I applied for the CDI 2.0 EG. Any help
> to get me started is highly appreciated!
>
> This will be an interesting time. I am looking forward to work with you!
>
> Regards,
> Thorben
>
>
> 2014-08-27 14:21 GMT+02:00 Antonio Goncalves <antonio.goncalves(a)gmail.com
> >:
>
> > The JCP.Next has added the role of "Members".
> >
> > Basically, to be "officially" part of the Expert Group you need to sign
> > the JSPA (https://jcp.org/aboutJava/communityprocess/JSPA2.pdf), apply
> to
> > be a JCP Member (https://jcp.org/ja/participation/membership_submit) and
> > then the Spec Lead gets you in (or not). If you are not officially a JCP
> > Member, you can be a "Member" (https://java.net/jira/browse/JCPNEXT4-8).
> >
> > Don't ask me more, I think here ends my knowledge of the JCP ;o)
> >
> > Antonio
> >
> >
> > On Wed, Aug 27, 2014 at 1:59 PM, Filipe Portes <omeuefilipe(a)gmail.com>
> > wrote:
> >
> >> thanks everybody for the welcome!!
> >>
> >> I have good Java EE and java 8 skills, and some experience with OSGi and
> >> modularity patterns! would be glad to help in any way!!
> >>
> >>
> >> On Wed, Aug 27, 2014 at 8:50 AM, Thomas Pepio <thomas.pepio(a)gmail.com>
> >> wrote:
> >>
> >>> Hi everyone,
> >>>
> >>>
> >>> My name is Thomas, and seeing all these mails about CDI 2.0
> >>> contributions decided me about getting out of my cave :).
> >>>
> >>> I'm not a JCP member, and was never involved in any open source project
> >>> (let me know if this is a problem). Sill I'd be happy to join the
> effort on
> >>> JSR-365 in any way !
> >>>
> >>>
> >>> Regards,
> >>> Thomas.
> >>>
> >>>
> >>> 2014-08-27 13:03 GMT+02:00 John D. Ament <john.d.ament(a)gmail.com>:
> >>>
> >>> I've formally thrown my hat into the ring too. This'll be fun.
> >>>>
> >>>>
> >>>> On Wed, Aug 27, 2014 at 6:37 AM, Antoine Sabot-Durand <
> >>>> antoine(a)sabot-durand.net> wrote:
> >>>>
> >>>>> I?m happy to count you in Antonio ! Your overall EE knowledge will be
> >>>>> very useful.
> >>>>>
> >>>>> Antoine
> >>>>>
> >>>>>
> >>>>> Le 27 ao?t 2014 ? 09:34, Antonio Goncalves <
> >>>>> antonio.goncalves(a)gmail.com> a ?crit :
> >>>>>
> >>>>> Antoine, you can count on me in the expert group ;o)
> >>>>>
> >>>>> Antonio
> >>>>>
> >>>>>
> >>>>> On Wed, Aug 27, 2014 at 9:30 AM, Antoine Sabot-Durand <
> >>>>> antoine(a)sabot-durand.net> wrote:
> >>>>>
> >>>>>> Hi Fillipe,
> >>>>>>
> >>>>>> You can either join the EG officially or bring your contribution
> >>>>>> outside the JCP. You can read our post on the subject :
> >>>>>> http://www.cdi-spec.org/news/2014/08/26/CDI-20_needs_you/
> >>>>>>
> >>>>>>
> >>>>>> Anyway, welcome onboard
> >>>>>>
> >>>>>> Antoine
> >>>>>>
> >>>>>>
> >>>>>> Welcome on
> >>>>>>
> >>>>>> Le 26 ao?t 2014 ? 23:02, Filipe Portes <omeuefilipe(a)gmail.com> a
> >>>>>> ?crit :
> >>>>>>
> >>>>>> Hello everyone!!
> >>>>>>
> >>>>>> my name is filipe(sounds like philip) portes, i'm a java developer
> >>>>>> and JUGLeader from Brazil,
> >>>>>> I'm part of @gojava and @soujava user groups and would like to join
> >>>>>> the efforts to the JSR-365.
> >>>>>>
> >>>>>> any advice you guys can give to start working will be awesome!
> >>>>>>
> >>>>>> Best Regards!
> >>>>>>
> >>>>>> --
> >>>>>> Filipe Portes - @filipeportes
> >>>>>> Senior Java EE/Web
> >>>>>> JUGLeader Gojava <http://www.gojava.org/> - @gojava
> >>>>>> _______________________________________________
> >>>>>> cdi-dev mailing list
> >>>>>> cdi-dev(a)lists.jboss.org
> >>>>>> https://lists.jboss.org/mailman/listinfo/cdi-dev
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> cdi-dev mailing list
> >>>>>> cdi-dev(a)lists.jboss.org
> >>>>>> https://lists.jboss.org/mailman/listinfo/cdi-dev
> >>>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Antonio Goncalves
> >>>>> Software architect, Java Champion and Pluralsight author
> >>>>>
> >>>>> Web site <http://www.antoniogoncalves.org/> | Twitter
> >>>>> <http://twitter.com/agoncal> | LinkedIn
> >>>>> <http://www.linkedin.com/in/agoncal> | Pluralsight
> >>>>> <http://pluralsight.com/training/Authors/Details/antonio-goncalves>
> | Paris
> >>>>> JUG <http://www.parisjug.org/> | Devoxx France <
> http://www.devoxx.fr/>
> >>>>>
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> cdi-dev mailing list
> >>>>> cdi-dev(a)lists.jboss.org
> >>>>> https://lists.jboss.org/mailman/listinfo/cdi-dev
> >>>>>
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> cdi-dev mailing list
> >>>> cdi-dev(a)lists.jboss.org
> >>>> https://lists.jboss.org/mailman/listinfo/cdi-dev
> >>>>
> >>>
> >>>
> >>> _______________________________________________
> >>> cdi-dev mailing list
> >>> cdi-dev(a)lists.jboss.org
> >>> https://lists.jboss.org/mailman/listinfo/cdi-dev
> >>>
> >>
> >>
> >>
> >> --
> >> Filipe Portes - @filipeportes
> >> Senior Java EE/Web
> >> JUGLeader Gojava <http://www.gojava.org/> - @gojava
> >>
> >> _______________________________________________
> >> cdi-dev mailing list
> >> cdi-dev(a)lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/cdi-dev
> >>
> >
> >
> >
> > --
> > Antonio Goncalves
> > Software architect, Java Champion and Pluralsight author
> >
> > Web site <http://www.antoniogoncalves.org> | Twitter
> > <http://twitter.com/agoncal> | LinkedIn
> > <http://www.linkedin.com/in/agoncal> | Pluralsight
> > <http://pluralsight.com/training/Authors/Details/antonio-goncalves> |
> Paris
> > JUG <http://www.parisjug.org> | Devoxx France <http://www.devoxx.fr>
> >
> > _______________________________________________
> > 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 [1] provided on this list, the provider waives all
> > patent and other intellectual property rights inherent in such
> information.
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://lists.jboss.org/pipermail/cdi-dev/attachments/20140829/4455b69b/at...
>
> ------------------------------
>
> Message: 3
> Date: Fri, 29 Aug 2014 21:36:51 +0200
> From: Thorben Janssen <thjanssen123(a)gmail.com>
> Subject: Re: [cdi-dev] EG membership status
> To: "John D. Ament" <john.d.ament(a)gmail.com>
> Cc: cdi-dev <cdi-dev(a)lists.jboss.org>
> Message-ID:
> <
> CAE9nDy8Lxo1pFzxE_mWEPwS9KZ+RE0+0Gm4mVeMYYT3n7Y6STg(a)mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> I am probably one of the missing Exhibit Bs. I got the request on Wednesday
> and send it on the same day.
> No response since then. We will see ...
>
> Thorben
>
>
> 2014-08-29 17:49 GMT+02:00 John D. Ament <john.d.ament(a)gmail.com>:
>
> > Hi,
> >
> > Hopefully I'm one of those waiting in JSPA (at least based on other
> emails
> > seems that way). My signer's out til next week due to US Labour Day.
> >
> > John
> >
> >
> > On Fri, Aug 29, 2014 at 10:08 AM, Antoine Sabot-Durand <
> > antoine(a)sabot-durand.net> wrote:
> >
> >> Hi All,
> >>
> >>
> >> Just to let you know that we received 9 requests to join the expert
> >> group. Pete and I have accepted all these requests but most of them are
> >> stuck at PMO level (if you don?t what the PMO is and want to learn some
> JCP
> >> slang, check here : https://jcp.org/en/procedures/jcp2_9)
> >>
> >> According to the PMO, 6 of you appear to have not provide Exhibit B to
> >> the JCP (Your company authorisation to work on the JSR). One is marked
> as
> >> not being a JCP member (probably the JSPA is missing). One is in process
> >> status and one has no PMO decision yet.
> >>
> >> In case you weren?t notified by the JCP.
> >>
> >> 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.
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://lists.jboss.org/pipermail/cdi-dev/attachments/20140829/a7066eec/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 45, Issue 17
> ***************************************
>
10 years, 3 months
EG membership status
by Antoine Sabot-Durand
Hi All,
Just to let you know that we received 9 requests to join the expert group. Pete and I have accepted all these requests but most of them are stuck at PMO level (if you don’t what the PMO is and want to learn some JCP slang, check here : https://jcp.org/en/procedures/jcp2_9 <https://jcp.org/en/procedures/jcp2_9>)
According to the PMO, 6 of you appear to have not provide Exhibit B to the JCP (Your company authorisation to work on the JSR). One is marked as not being a JCP member (probably the JSPA is missing). One is in process status and one has no PMO decision yet.
In case you weren’t notified by the JCP.
Antoine
10 years, 3 months
Introduce myself
by Filipe Portes
Hello everyone!!
my name is filipe(sounds like philip) portes, i'm a java developer and
JUGLeader from Brazil,
I'm part of @gojava and @soujava user groups and would like to join the
efforts to the JSR-365.
any advice you guys can give to start working will be awesome!
Best Regards!
--
Filipe Portes - @filipeportes
Senior Java EE/Web
JUGLeader Gojava <http://www.gojava.org/> - @gojava
10 years, 3 months
Working method for CDI 2.0 (a proposal)
by Antoine Sabot-Durand
Hi All,
So we are ready to start work on CDI 2.0. As you know or guess, CDI 2.0 is a great challenge : we have to enhance the existing spec (without breaking existing features), add new features and get the spec ready for new platform (Java SE mainly).
I’ve been thinking for a while how to lead such a vast project with the following constraints:
- Keep the big picture of the spec in mind while working on all detail of each new / modified features
- Have the right balance between the ideal specification and the implementation only driven specification approaches
- Be able to welcome new contributors without loosing them in spec history or advance technical details at the beginning
- Give visibility to third party (other JSR or future implementor) of the spec without forcing them to follow our ML, IRC, JIRA
- Get feedback from the community easily while designing the spec
So I came to the idea of creating different workshop on big different CDI features and goals. I identified these (the descriptions are only suggestions of task in the workshop, they should’ be discussed now)
- Modularity (Parts / Profiles) : how we can make CDI more modular by extracting sub part in the spec, like CDI light and events subparts
- Java SE features : how CDI should work in Java SE and what SPI should we add or standardise to ease its integration in home brewed stacks
- Events enhancement : bringing asynchronicity or ordering to events. Can it be extended to all Java EE
- Interceptor & Decorator : AOP support on produced or custom bean. Work with interceptor spec to add AOP on inner call
- SPI enhancement for integration : give access to all metadata produced by the container, give control of CDI from outside code, support Bean addition / modification @ Runtime
- Contexts enhancement : go beyond the the thread-bound request-response model used by context today to support new application architecture
- Java 8 enhancement : see how new features in java 8 (type annotation, annotation repetition, lambdas, streams, default methods, type inference…) could enhance CDI in existing and new features.
If you have other ideas they are welcome.
A workshop should be leaded by a contributor who has a good knowledge of the current spec. It would be composed by a group of contributors.
The goal of these workshop is to create ideas funnel to start from high level and go to details after wrong or impossible ideas had been filtered. The best way to avoid missing a new idea.
Depending of the workshop and the group I can think of 2 ways to create the funnel
— Long workflow
1) Brain storm. Use an online meeting, JIRA, mail exchange or shared doc, to have every workshop give ideas on the topic. Ideally there shouldn’t be censorship at this level.
2) Sorting ideas. All the ideas should be discussed by the group (JIRA is probably the best place to do that). At the end the group will have a bunch of refined ideas to work on
3) Blueprint draft. The workshop lead uses the ideas to create a draft document describing how the new feature or enhancement. Ideas not used are kept
4) Draft discussion The draft is commented, amended, enhanced by the group and when people feel ready by the EG
5) Spec enhancement. When an agreement is accepted on the doc, one of the EG member translate it for the spec (with all the rules)
— Short workflow for smaller groups or on narrower subject
1) Blueprint draft : the workgroup lead propose a draft document describing his global idea of how the future should work
2) Draft discussion The draft is commented, amended, enhanced by the group which can react to the doc by proposing new ideas. and When people feel ready by the EG
3) Spec enhancement. When an agreement is accepted on the doc, one of the EG member translate it for the spec (with all the rules)
Draft could be written on Google Drive or in Github (directly in Asciidoc format). Each solution has its pros and cons.
Existing tickets in Jira could be injected in the workflows below. Some that couldn’t (clarification or spec bugs) will be treated in the classical way.
Thanks for your feedback on this proposal,
Antoine
10 years, 3 months
[JBoss JIRA] (CDI-455) Allow building of TypeLiteral's with dynamic types
by Lucas Ventura Carro (JIRA)
[ https://issues.jboss.org/browse/CDI-455?page=com.atlassian.jira.plugin.sy... ]
Lucas Ventura Carro edited comment on CDI-455 at 8/28/14 5:12 AM:
------------------------------------------------------------------
As [~jharting] told in the mailing list, type safety cannot be guaranteed. But this will happen if the {{TypeLiteral}} has the raw and parameterized types as arguments. But IMHO the usual use case is that raw type is fixed, but not the parameterized types of it.
In example, following [this of guice|http://luisfsgoncalves.wordpress.com/2010/09/08/generic-bindings-wi...], CDI {{TypeLiteral}} could be built as:
{code}
new TypeLiteral(ChocolateEater.class, argument.getClass()){}
{code}
And efectively, type safety would be lost. But if we know that we will have an static {{ChocolateEater}} but a dynamic {{Chocolate}} parameter, we can have type safety and the {{TypeLiteral}} could be built as:
{code}
new TypeLiteral<ChocolateEater<? extends Chocolate>>(argument.getClass()){}
{code}
It is right?
was (Author: lucasvc):
As [~jharting] told in the mailing list, type safety cannot be guaranteed. But this will happen if the {{TypeLiteral}} has the raw and parameterized types as arguments. But IMHO the usual use case is that raw type is fixed, but not the parameterized types of it.
In example, following [this of guice|http://luisfsgoncalves.wordpress.com/2010/09/08/generic-bindings-wi...], CDI {{TypeLiteral}} could be built as:
{code}
new TypeLiteral(ChocolateEater.class, argument.getClass()){}
{code}
And efectively, type safety would be lost. But if we know that we will have an static {{ChocolateEater}} but a dynamic {{Chocolate}} parameter, we can have type safety and the {{TypeLiteral}} could be built as:
{code}
new TypeLiteral<ChocolateEater<? extends Chocolate>>(argument.getClass()){}
{code}
I'm I correct?
> Allow building of TypeLiteral's with dynamic types
> --------------------------------------------------
>
> Key: CDI-455
> URL: https://issues.jboss.org/browse/CDI-455
> Project: CDI Specification Issues
> Issue Type: Feature Request
> Reporter: Lucas Ventura Carro
>
> It could be useful the building of {{TypeLiteral}}'s, but using dynamic types. This way, the types can be indicated at runtime and not in compile. This functionality is "doable" as it is done at [Guice|https://github.com/google/guice], a similar injection framework, and as [this post shows|http://luisfsgoncalves.wordpress.com/2010/09/08/generic-bindings-wi...].
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 3 months
[JBoss JIRA] (CDI-455) Allow building of TypeLiteral's with dynamic types
by Lucas Ventura Carro (JIRA)
[ https://issues.jboss.org/browse/CDI-455?page=com.atlassian.jira.plugin.sy... ]
Lucas Ventura Carro commented on CDI-455:
-----------------------------------------
As [~jharting] told in the mailing list, type safety cannot be guaranteed. But this will happen if the {{TypeLiteral}} has the raw and parameterized types as arguments. But IMHO the usual use case is that raw type is fixed, but not the parameterized types of it.
In example, following [this of guice|http://luisfsgoncalves.wordpress.com/2010/09/08/generic-bindings-wi...], CDI {{TypeLiteral}} could be built as:
{code}
new TypeLiteral(ChocolateEater.class, argument.getClass()){}
{code}
And efectively, type safety would be lost. But if we know that we will have an static {{ChocolateEater}} but a dynamic {{Chocolate}} parameter, we can have type safety and the {{TypeLiteral}} could be built as:
{code}
new TypeLiteral<ChocolateEater<? extends Chocolate>>(argument.getClass()){}
{code}
I'm I correct?
> Allow building of TypeLiteral's with dynamic types
> --------------------------------------------------
>
> Key: CDI-455
> URL: https://issues.jboss.org/browse/CDI-455
> Project: CDI Specification Issues
> Issue Type: Feature Request
> Reporter: Lucas Ventura Carro
>
> It could be useful the building of {{TypeLiteral}}'s, but using dynamic types. This way, the types can be indicated at runtime and not in compile. This functionality is "doable" as it is done at [Guice|https://github.com/google/guice], a similar injection framework, and as [this post shows|http://luisfsgoncalves.wordpress.com/2010/09/08/generic-bindings-wi...].
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years, 3 months
Switching from old IRC channel : #jsr346 to #cdi-dev
by Antoine Sabot-Durand
Hi,
For those who are using the old IRC channel (#jsr346) we have created a new channel : #cdi-dev on freenode. Please switch to the new channel to stay in contact with us on IRC.
Antoine Sabot-Durand
10 years, 3 months
Re: [cdi-dev] cdi-dev Digest, Vol 45, Issue 12
by Werner Keil
Antonio/all,
Putting on my "JCP EC Hat" for this as I'm also the only current Individual
Member in the EC and JCP.next working groups, "Member" is not exactly
right, but there shall be other Mamber categories, mainly "Partner" (stands
for a JUG, whether only the JUG as a whole joined an EG or members on
behalf, we'll flesh out in JSR 364) and one that's currently named
"Contributor".
And of course the so called "Affiliate" role.
All require at least a "light" form of JCP Membership, either you need to
fill something out (similar to Apache or Eclipse, especially the new
"Contributor Agreement") and scan/fax or submit an online form. The first
level that already exists is an "Observer". Which does not require formal
membership, you simply join via an online form. All JSRs hosted on java.net
allow a user to join a project and their default status until changed is
"Observer". Please ask the Spec Leads how becoming an observer works for
CDI 2, but according to the detail page, if you subscribed to THIS list,
you already ARE one;-D
Until JSR 364 is final, you only have the option to remain an observer
(e.g. what Thomas explained he might be comfortable with this at the
moment;-) or become a full member. As an employee you need permission by
your company, if you are student, freelancer, etc. you can join all by
yourself and sign the JSPA.
Regards,
Werner Keil | JCP Executive Committee Member, JSR 363 Co Spec Lead |
Eclipse UOMo Lead, Babel Language Champion | Apache Committer
Twitter @wernerkeil | @UnitAPI | @JSR354 | #EclipseUOMo | #Java_Social |
#DevOps
Skype werner.keil | Google+ gplus.to/wernerkeil
On Wed, Aug 27, 2014 at 2:21 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: Introduce myself (Thomas Pepio)
> 2. Re: Introduce myself (Filipe Portes)
> 3. Re: Introduce myself (Antonio Goncalves)
>
> ------------------------------
>
> Message: 3
> Date: Wed, 27 Aug 2014 14:21:02 +0200
> From: Antonio Goncalves <antonio.goncalves(a)gmail.com>
> Subject: Re: [cdi-dev] Introduce myself
> To: Filipe Portes <omeuefilipe(a)gmail.com>
> Cc: cdi-dev <cdi-dev(a)lists.jboss.org>
> Message-ID:
> <CA+ZZq9_a5NW-t5+NbH7_Vox=6M0xUGgZoRyOogHde4KsYfNW=
> A(a)mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> The JCP.Next has added the role of "Members".
>
> Basically, to be "officially" part of the Expert Group you need to sign the
> JSPA (https://jcp.org/aboutJava/communityprocess/JSPA2.pdf), apply to be a
> JCP Member (https://jcp.org/ja/participation/membership_submit) and then
> the Spec Lead gets you in (or not). If you are not officially a JCP Member,
> you can be a "Member" (https://java.net/jira/browse/JCPNEXT4-8).
>
> Don't ask me more, I think here ends my knowledge of the JCP ;o)
>
> Antonio
>
>
> On Wed, Aug 27, 2014 at 1:59 PM, Filipe Portes <omeuefilipe(a)gmail.com>
> wrote:
>
> > thanks everybody for the welcome!!
> >
> > I have good Java EE and java 8 skills, and some experience with OSGi and
> > modularity patterns! would be glad to help in any way!!
> >
> >
> > On Wed, Aug 27, 2014 at 8:50 AM, Thomas Pepio <thomas.pepio(a)gmail.com>
> > wrote:
> >
> >> Hi everyone,
> >>
> >>
> >> My name is Thomas, and seeing all these mails about CDI 2.0
> contributions
> >> decided me about getting out of my cave :).
> >>
> >> I'm not a JCP member, and was never involved in any open source project
> >> (let me know if this is a problem). Sill I'd be happy to join the
> effort on
> >> JSR-365 in any way !
> >>
> >>
> >> Regards,
> >> Thomas.
> >>
> >>
> >> 2014-08-27 13:03 GMT+02:00 John D. Ament <john.d.ament(a)gmail.com>:
> >>
> >> I've formally thrown my hat into the ring too. This'll be fun.
> >>>
> >>>
> >>> On Wed, Aug 27, 2014 at 6:37 AM, Antoine Sabot-Durand <
> >>> antoine(a)sabot-durand.net> wrote:
> >>>
> >>>> I?m happy to count you in Antonio ! Your overall EE knowledge will be
> >>>> very useful.
> >>>>
> >>>> Antoine
> >>>>
> >>>>
> >>>> Le 27 ao?t 2014 ? 09:34, Antonio Goncalves <
> antonio.goncalves(a)gmail.com>
> >>>> a ?crit :
> >>>>
> >>>> Antoine, you can count on me in the expert group ;o)
> >>>>
> >>>> Antonio
> >>>>
> >>>>
> >>>> On Wed, Aug 27, 2014 at 9:30 AM, Antoine Sabot-Durand <
> >>>> antoine(a)sabot-durand.net> wrote:
> >>>>
> >>>>> Hi Fillipe,
> >>>>>
> >>>>> You can either join the EG officially or bring your contribution
> >>>>> outside the JCP. You can read our post on the subject :
> >>>>> http://www.cdi-spec.org/news/2014/08/26/CDI-20_needs_you/
> >>>>>
> >>>>>
> >>>>> Anyway, welcome onboard
> >>>>>
> >>>>> Antoine
> >>>>>
> >>>>>
> >>>>> Welcome on
> >>>>>
> >>>>> Le 26 ao?t 2014 ? 23:02, Filipe Portes <omeuefilipe(a)gmail.com> a
> >>>>> ?crit :
> >>>>>
> >>>>> Hello everyone!!
> >>>>>
> >>>>> my name is filipe(sounds like philip) portes, i'm a java developer
> and
> >>>>> JUGLeader from Brazil,
> >>>>> I'm part of @gojava and @soujava user groups and would like to join
> >>>>> the efforts to the JSR-365.
> >>>>>
> >>>>> any advice you guys can give to start working will be awesome!
> >>>>>
> >>>>> Best Regards!
> >>>>>
> >>>>> --
> >>>>> Filipe Portes - @filipeportes
> >>>>> Senior Java EE/Web
> >>>>> JUGLeader Gojava <http://www.gojava.org/> - @gojava
> >>>>> _______________________________________________
> >>>>> cdi-dev mailing list
> >>>>> cdi-dev(a)lists.jboss.org
> >>>>> https://lists.jboss.org/mailman/listinfo/cdi-dev
> >>>>>
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> cdi-dev mailing list
> >>>>> cdi-dev(a)lists.jboss.org
> >>>>> https://lists.jboss.org/mailman/listinfo/cdi-dev
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Antonio Goncalves
> >>>> Software architect, Java Champion and Pluralsight author
> >>>>
> >>>> Web site <http://www.antoniogoncalves.org/> | Twitter
> >>>> <http://twitter.com/agoncal> | LinkedIn
> >>>> <http://www.linkedin.com/in/agoncal> | Pluralsight
> >>>> <http://pluralsight.com/training/Authors/Details/antonio-goncalves>
> | Paris
> >>>> JUG <http://www.parisjug.org/> | Devoxx France <http://www.devoxx.fr/
> >
> >>>>
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> cdi-dev mailing list
> >>>> cdi-dev(a)lists.jboss.org
> >>>> https://lists.jboss.org/mailman/listinfo/cdi-dev
> >>>>
> >>>
> >>>
> >>> _______________________________________________
> >>> cdi-dev mailing list
> >>> cdi-dev(a)lists.jboss.org
> >>> https://lists.jboss.org/mailman/listinfo/cdi-dev
> >>>
> >>
> >>
> >> _______________________________________________
> >> cdi-dev mailing list
> >> cdi-dev(a)lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/cdi-dev
> >>
> >
> >
> >
> > --
> > Filipe Portes - @filipeportes
> > Senior Java EE/Web
> > JUGLeader Gojava <http://www.gojava.org/> - @gojava
> >
> > _______________________________________________
> > cdi-dev mailing list
> > cdi-dev(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/cdi-dev
> >
>
>
>
> --
> Antonio Goncalves
> Software architect, Java Champion and Pluralsight author
>
> Web site <http://www.antoniogoncalves.org> | Twitter
> <http://twitter.com/agoncal> | LinkedIn <
> http://www.linkedin.com/in/agoncal> |
> Pluralsight
> <http://pluralsight.com/training/Authors/Details/antonio-goncalves> |
> Paris
> JUG <http://www.parisjug.org> | Devoxx France <http://www.devoxx.fr>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://lists.jboss.org/pipermail/cdi-dev/attachments/20140827/b9ceb529/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 [1] provided on this list, the provider waives all
> patent and other intellectual property rights inherent in such information.
>
> End of cdi-dev Digest, Vol 45, Issue 12
> ***************************************
>
10 years, 3 months
