[JBoss JIRA] (CDI-438) Fix type parameters ordering in ProcessProducerMethod and ProcessProducerField events
by Martin Kouba (JIRA)
[ https://issues.jboss.org/browse/CDI-438?page=com.atlassian.jira.plugin.sy... ]
Martin Kouba updated CDI-438:
-----------------------------
Description:
Since CDI 1.0 there is an inconsistency in the description of {{ProcessProducerMethod}} event...
The text:
{quote}
For a producer method with method **return type X** of a bean with **bean class T**, the container must raise an event of type ProcessProducerMethod<T, X>.
{quote}
API:
{code:java}
/**
* @param <T> The return type of the producer method
* @param <X> The class of the bean declaring the producer method
*/
public interface ProcessProducerMethod<T, X> extends ProcessBean<X> {
}
{code}
The same applies to {{ProcessProducerField}}.
TCK and RI (Weld) follow the API. As one of the consequences an {{ProcessProducerMethod<Foo,Producer>}} event is not delivered to an observer with the event parameter {{ProcessBean<Foo>}} - which is required by the spec but does not make sense at the same time.
It's obvious that JCP compatibility rules required to keep the wrong ordering for CDI 1.x (see also the comments in {{javax.enterprise.inject.spi.ProcessProducerMethod}}). I believe this should be fixed in CDI 2.0.
was:
Since CDI 1.0 there is an inconsistency in the description of {{ProcessProducerMethod}} event...
The text:
{quote}
For a producer method with method return type X of a bean with bean class T, the container must raise an event of type ProcessProducerMethod<T, X>.
{quote}
API:
{code:java}
/**
* @param <T> The return type of the producer method
* @param <X> The class of the bean declaring the producer method
*/
public interface ProcessProducerMethod<T, X> extends ProcessBean<X> {
}
{code}
The same applies to {{ProcessProducerField}}.
TCK and RI (Weld) follow the API. As one of the consequences an {{ProcessProducerMethod<Foo,Producer>}} event is not delivered to an observer with the event parameter {{ProcessBean<Foo>}}.
It's obvious that JCP compatibility rules required to keep the wrong ordering for CDI 1.x (see also the comments in {{javax.enterprise.inject.spi.ProcessProducerMethod}}). I believe this should be fixed in CDI 2.0.
> Fix type parameters ordering in ProcessProducerMethod and ProcessProducerField events
> -------------------------------------------------------------------------------------
>
> Key: CDI-438
> URL: https://issues.jboss.org/browse/CDI-438
> Project: CDI Specification Issues
> Issue Type: Bug
> Affects Versions: 1.2.Final
> Reporter: Martin Kouba
>
> Since CDI 1.0 there is an inconsistency in the description of {{ProcessProducerMethod}} event...
> The text:
> {quote}
> For a producer method with method **return type X** of a bean with **bean class T**, the container must raise an event of type ProcessProducerMethod<T, X>.
> {quote}
> API:
> {code:java}
> /**
> * @param <T> The return type of the producer method
> * @param <X> The class of the bean declaring the producer method
> */
> public interface ProcessProducerMethod<T, X> extends ProcessBean<X> {
> }
> {code}
> The same applies to {{ProcessProducerField}}.
> TCK and RI (Weld) follow the API. As one of the consequences an {{ProcessProducerMethod<Foo,Producer>}} event is not delivered to an observer with the event parameter {{ProcessBean<Foo>}} - which is required by the spec but does not make sense at the same time.
> It's obvious that JCP compatibility rules required to keep the wrong ordering for CDI 1.x (see also the comments in {{javax.enterprise.inject.spi.ProcessProducerMethod}}). I believe this should be fixed in CDI 2.0.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (CDI-385) ProcessObserverMethod is different btw spec and API
by Tomas Remes (JIRA)
[ https://issues.jboss.org/browse/CDI-385?page=com.atlassian.jira.plugin.sy... ]
Tomas Remes commented on CDI-385:
---------------------------------
[~antoinesabot-durand] There is old comment (" // These parameters are the wrong .." ) on javax.enterprise.inject.spi.ProcessObserverMethod which should be removed.
> ProcessObserverMethod is different btw spec and API
> ---------------------------------------------------
>
> Key: CDI-385
> URL: https://issues.jboss.org/browse/CDI-385
> Project: CDI Specification Issues
> Issue Type: Bug
> Components: Javadoc and API
> Affects Versions: 1.1.PFD
> Reporter: Mark Struberg
> Assignee: Antoine Sabot-Durand
> Priority: Critical
> Labels: CDI_spec_chge, Ready_to_fix
> Fix For: 1.2.Final
>
>
> As stated in CDI-88 the spec and API is different for ProcessObserverMethod.
> In the spec there is a method
> public AnnotatedParameter<T> getAnnotatedEventParameter();
> but in the API there is
> AnnotatedMethod<X> getAnnotatedMethod();
> which imo makes much more sense anyway.
> Thus we should amend the spec wording finally.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
Enhancing SPI to support async operation for contexts
by Antoine Sabot-Durand
Hi All,
Beyond the asynchronous event case, shouldn’t we provide a way for user to launch async treatments in CDI with the possibility to keep the existing contexts at the moment of async operation launch?
Today servlet or JAX-RS spec support async call without the loss of request for instance. Shouldn’t we think to something like that?
Thanks for your input on that point.
Antoine
10 years
Re: [cdi-dev] Meet our new ambassador
by Werner Keil
Aside from the image, whatever name he ends up with, given the whole
Arquillian project heavily (and directly) borrows from a well known movie
franchise, should there be at least an "inspiration" for his name from
another, it looks like we're safe there, too?;-)
Werner
On Thu, Feb 19, 2015 at 6:56 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: Enhancing SPI to support async operation for contexts
> (Mark Struberg)
> 2. Re: Enhancing SPI to support async operation for contexts
> (Mark Struberg)
> 3. Re: Meet our new ambassador (Antoine Sabot-Durand)
>
>
> ----------------------------------------------------------------------
>
>
> Message: 3
> Date: Thu, 19 Feb 2015 18:56:43 +0100
> From: Antoine Sabot-Durand <antoine(a)sabot-durand.net>
> Subject: Re: [cdi-dev] Meet our new ambassador
> To: Pete Muir <pmuir(a)redhat.com>
> Cc: cdi-dev <cdi-dev(a)lists.jboss.org>
> Message-ID: <20811EED-FF1A-4262-86F0-C0EF47DFA925(a)sabot-durand.net>
> Content-Type: text/plain; charset="utf-8"
>
> After legal check. These elements are under Creative Commons
> Attribution-NonCommercial-NoDerivatives 4.0 International (CC BY-NC-ND 4.0).
>
> so more concretely the details are:
>
> ? Share ? copy and redistribute the material in any medium or format
> ? The licensor cannot revoke these freedoms as long as you follow the
> license terms.
>
> Under the following terms:
>
> ? Attribution ? You must give appropriate credit, provide a link to the
> license, and indicate if changes were made. You may do so in any reasonable
> manner, but not in any way that suggests the licensor endorses you or your
> use.
> ? NonCommercial ? You may not use the material for commercial purposes.
> ? NoDerivatives ? If you remix, transform, or build upon the material, you
> may not distribute the modified material.
> ? No additional restrictions ? You may not apply legal terms or
> technological measures that legally restrict others from doing anything the
> license permits.
>
>
> Antoine
>
> > Le 19 f?vr. 2015 ? 16:20, Pete Muir <pmuir(a)redhat.com> a ?crit :
> >
> > We are looking in to this, stay tuned :-)
> >
> >> On 19 Feb 2015, at 11:45, Thorben Janssen <thjanssen123(a)gmail.com
> <mailto:thjanssen123@gmail.com>> wrote:
> >>
> >> Hi Antoine,
> >>
> >> under which license are the images licensed?
> >> I was told, that most of the JBoss related logos (in that specific case
> Arquillian) are licensed under a closed one. If that is also the case for
> the CDI logo, we should better not use it for any social media post or
> article that is not published on the CDI website.
> >>
> >> Regards,
> >> Thorben
> >>
> >> --
> >> Thorben Janssen
> >>
> >> @thjanssen123 <https://twitter.com/thjanssen123>
> >> www.thoughts-on-java.org <http://www.thoughts-on-java.org/>
> >>
> >> 2015-02-19 11:04 GMT+01:00 Antoine Sabot-Durand <
> antoine(a)sabot-durand.net <mailto:antoine@sabot-durand.net>>:
> >> Hi All,
> >>
> >>
> >> With the idea to increase CDI notoriety we ask JBoss design team to
> work on CDI Logo. Creating an identity for something as abstract as CDI is
> not very easy so we asked the design team to avoid corporate logo and give
> a true identity to CDI thru a mascot.
> >> So meet our new ambassador and logo :
> >> <PastedGraphic-2.png>
> >>
> >> I have a bunch of graphic elements (
> http://design.jboss.org/cdi/index.htm <
> http://design.jboss.org/cdi/index.htm>) to switch our look and feel on
> the web and on social network. We?re even ready to have T-Shirts and other
> swag that can be ordered here:
> >>
> >> http://www.cafepress.com/jbossorg/12231128 <
> http://www.cafepress.com/jbossorg/12231128>
> >>
> >> These stuff will make nice giveaways for conferences to help creating a
> CDI brand and raise the adoption of the spec.
> >>
> >> Now, this bearded fellow has still no name. Cildmi was the first name
> to come to my mind, but perhaps you have better ideas?
> >>
> >> Regards,
> >>
> >> Antoine
> >>
> >> _______________________________________________
> >> 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.
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://lists.jboss.org/pipermail/cdi-dev/attachments/20150219/c28762ac/at...
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 495 bytes
> Desc: Message signed with OpenPGP using GPGMail
> Url :
> http://lists.jboss.org/pipermail/cdi-dev/attachments/20150219/c28762ac/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 51, Issue 36
> ***************************************
>
10 years
Meet our new ambassador
by Antoine Sabot-Durand
Hi All,
With the idea to increase CDI notoriety we ask JBoss design team to work on CDI Logo. Creating an identity for something as abstract as CDI is not very easy so we asked the design team to avoid corporate logo and give a true identity to CDI thru a mascot.
So meet our new ambassador and logo :
I have a bunch of graphic elements (http://design.jboss.org/cdi/index.htm) to switch our look and feel on the web and on social network. We’re even ready to have T-Shirts and other swag that can be ordered here:
http://www.cafepress.com/jbossorg/12231128 <http://www.cafepress.com/jbossorg/12231128>
These stuff will make nice giveaways for conferences to help creating a CDI brand and raise the adoption of the spec.
Now, this bearded fellow has still no name. Cildmi was the first name to come to my mind, but perhaps you have better ideas?
Regards,
Antoine
10 years
Re: [cdi-dev] Meet our new ambassador
by Werner Keil
+1
CDImli was the first thing I imagined before even reading the rest of your
mail;-)
Werner
On Thu, Feb 19, 2015 at 12:45 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. Enhancing SPI to support async operation for contexts
> (Antoine Sabot-Durand)
> 2. Meet our new ambassador (Antoine Sabot-Durand)
> 3. Re: Enhancing SPI to support async operation for contexts
> (Romain Manni-Bucau)
> 4. Revamped blog section on the site (Antoine Sabot-Durand)
> 5. Re: Meet our new ambassador (Thorben Janssen)
>
>
> ----------------------------------------------------------------------
>
>
>
> Message: 2
> Date: Thu, 19 Feb 2015 11:04:31 +0100
> From: Antoine Sabot-Durand <antoine(a)sabot-durand.net>
> Subject: [cdi-dev] Meet our new ambassador
> To: cdi-dev <cdi-dev(a)lists.jboss.org>
> Message-ID: <559D9756-82CB-451F-9D2D-A1DCD9246854(a)sabot-durand.net>
> Content-Type: text/plain; charset="utf-8"
>
> Hi All,
>
>
> With the idea to increase CDI notoriety we ask JBoss design team to work
> on CDI Logo. Creating an identity for something as abstract as CDI is not
> very easy so we asked the design team to avoid corporate logo and give a
> true identity to CDI thru a mascot.
> So meet our new ambassador and logo :
>
>
> I have a bunch of graphic elements (http://design.jboss.org/cdi/index.htm)
> to switch our look and feel on the web and on social network. We?re even
> ready to have T-Shirts and other swag that can be ordered here:
>
> http://www.cafepress.com/jbossorg/12231128 <
> http://www.cafepress.com/jbossorg/12231128>
>
> These stuff will make nice giveaways for conferences to help creating a
> CDI brand and raise the adoption of the spec.
>
> Now, this bearded fellow has still no name. Cildmi was the first name to
> come to my mind, but perhaps you have better ideas?
>
> Regards,
>
> Antoine
> -------------- next part --------------
>
> End of cdi-dev Digest, Vol 51, Issue 31
> ***************************************
>
10 years
Re: [cdi-dev] Unavailable for today meeting
by Werner Keil
Antoine/all,
Sorry to hear.
Btw, since CDI is hosted by GitHub, maybe some of you saw the new Gitter
chat feature Raj kindly invited me to the other day. JSR 377 started using
it: https://gitter.im/jsr377, I also created a similar room for Agorava
https://gitter.im/agorava
Would that be an option for future chat sessions or do you prefer IRC?
Even though there is at least one working Web client, it seems far less
intuitive than Gitter at least in my impression.
Gitter automatically persists all sessions, and though there wasn't enough
time to fully test it, an archive link like
https://gitter.im/jsr377/archives/all suggests, conversations won't be
thrown away too easily or may even stay there forever;-)
Cheers,
Werner
On Wed, Feb 18, 2015 at 4:16 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: Extension handling in EARs (arjan tijms)
> 2. Re: Extension handling in EARs (Mark Struberg)
> 3. Re: Extension handling in EARs (Romain Manni-Bucau)
> 4. Re: Extension handling in EARs (Jozef Hartinger)
> 5. Re: Extension handling in EARs (Jozef Hartinger)
> 6. Unavailable for today meeting (Antoine Sabot-Durand)
> 7. [JBoss JIRA] (CDI-498) Revise "6.7.5. The Conversation
> interface" - dots are not valid in EL name
> (SBS JIRA Integration (JIRA))
>
>
> ------------------------------
>
> Message: 6
> Date: Wed, 18 Feb 2015 16:03:50 +0100
> From: Antoine Sabot-Durand <antoine(a)sabot-durand.net>
> Subject: [cdi-dev] Unavailable for today meeting
> To: cdi-dev <cdi-dev(a)lists.jboss.org>
> Message-ID: <2C1BFB26-6D06-4FFA-99D5-2E0E2E30C40C(a)sabot-durand.net>
> Content-Type: text/plain; charset="utf-8"
>
> Hi guys,
>
>
> I won?t make it for today. Let?s schedule meeting for net wednesday.
>
> Sorry,
>
> 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.
>
> End of cdi-dev Digest, Vol 51, Issue 28
> ***************************************
>
10 years
Unavailable for today meeting
by Antoine Sabot-Durand
Hi guys,
I won’t make it for today. Let’s schedule meeting for net wednesday.
Sorry,
Antoine
10 years
