From useyour.mind at gmail.com  Fri Aug  1 11:51:10 2014
From: useyour.mind at gmail.com (Luc)
Date: Fri, 1 Aug 2014 17:51:10 +0200
Subject: [cdi-dev] Dynamic 'TypeLiteral' with ParameterizedType,
	such as Guice
Message-ID: <CAJvqtSp0896tNY+TCkv49PZye1OgNNOacTtAkrBtrU_TGcrjXA@mail.gmail.com>

Hi,

Today I realized about the method
'javax.enterprise.inject.Instance#select(javax.enterprise.util.TypeLiteral,
java.lang.annotation.Annotation...)' [1], which whas there from 1.0 version.
After watching CDI 'TypeLiteral' implementation, came a question to mind to
me:

  Could be done the same, but *with dynamic class type building*?

And my first google search bring me to a post where a user told some of the
benefits of Guice [2] injection and dynamic types [3], which was written at
2010, and it covers exactly my actual needs.
After watching more the 'TypeLiteral' from CDI and how it is done with
Guice, I thought that could be cool to have this feature in CDI too. I know
I can do it for my own project (and I will) but I have a few questions:

  * Should I open an issue at CDI Jira? Or is more a Weld issue?
  * If the issue is open, I'd like to contribute to its development. A part
of the "easy rules" from http://www.cdi-spec.org/contribute/, what more
should I do?

Thanks!!

  [1]:
http://docs.jboss.org/cdi/api/1.0-SP4/javax/enterprise/inject/Instance.html#select(javax.enterprise.util.TypeLiteral,
java.lang.annotation.Annotation...)
  [2]: https://github.com/google/guice
  [3]:
http://luisfsgoncalves.wordpress.com/2010/09/08/generic-bindings-with-guice/

--
Lucas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20140801/d171307c/attachment-0001.html 

From mpaluch at paluch.biz  Fri Aug  1 14:16:17 2014
From: mpaluch at paluch.biz (Mark Paluch)
Date: Fri, 1 Aug 2014 20:16:17 +0200
Subject: [cdi-dev] Proposal: Improve producer method signature capability by
	accepting qualifier annotations
Message-ID: <5F237A8E-71BA-4B7A-9962-257E24C67F06@paluch.biz>

CDI supports producer methods which accept the InjectionPoint as argument which allows to access all metadata to the injection point. The InjectionPoint approach adds a certain complexity which is not needed when only qualifier metadata has to be processed. I propose to allow annotation types within the producer method signatures. Code example for a use case: 

{code}
@HttpParam("username") @Inject String username
{code}

{code}
import javax.enterprise.inject.Produces;
import javax.enterprise.inject.spi.InjectionPoint;

class HttpParams
   @Produces

   String getParamValue(HttpParam httpParam) {

      ServletRequest request = (ServletRequest) FacesContext.getCurrentInstance().getExternalContext().getRequest();
	  
      return request.getParameter(httpParam.value());
	  
      // current support looks like:
      // String getParamValue(InjectionPoint ip) {
      // return request.getParameter(ip.getAnnotated().getAnnotation(HttpParam.class).value());

   }
}
{code}

Producer methods accepting qualifier annotations ensure to have always an annotation instance, this helps to prevent null pointer access since InjectionPoint.getAnnotated().getAnnotation(java.lang.Class<T>) may return null.

Best regards, Mark

--

PALUCH.biz
Heckenpfad 14 // 69469 Weinheim
T. 0 62 01/65 04 24-0 // F. 0 62 01/65 04 24-9
mpaluch at paluch.biz
http://www.paluch.biz

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20140801/42cd724e/attachment.html 

From pmuir at redhat.com  Tue Aug  5 07:26:48 2014
From: pmuir at redhat.com (Pete Muir)
Date: Tue, 5 Aug 2014 12:26:48 +0100
Subject: [cdi-dev] Proposal: Improve producer method signature
	capability by accepting qualifier annotations
In-Reply-To: <5F237A8E-71BA-4B7A-9962-257E24C67F06@paluch.biz>
References: <5F237A8E-71BA-4B7A-9962-257E24C67F06@paluch.biz>
Message-ID: <6B32FA74-D79C-4504-ADA7-07E28E27EF89@redhat.com>

HI Mark,

Thanks for the suggestion. Can you file a JIRA (http://issues.jboss.org/browse/CDI) so we don?t loose this?

Pete

On 1 Aug 2014, at 19:16, Mark Paluch <mpaluch at paluch.biz> wrote:

> CDI supports producer methods which accept the InjectionPoint as argument which allows to access all metadata to the injection point. The InjectionPoint approach adds a certain complexity which is not needed when only qualifier metadata has to be processed. I propose to allow annotation types within the producer method signatures. Code example for a use case: 
> 
> {code}
> @HttpParam("username") @Inject String username
> {code}
> 
> {code}
> import javax.enterprise.inject.Produces;
> import javax.enterprise.inject.spi.InjectionPoint;
> 
> class HttpParams
>    @Produces
> 
>    String getParamValue(HttpParam httpParam) {
> 
>       ServletRequest request = (ServletRequest) FacesContext.getCurrentInstance().getExternalContext().getRequest();
> 	  
>       return request.getParameter(httpParam.value());
> 	  
>       // current support looks like:
>       // String getParamValue(InjectionPoint ip) {
>       // return request.getParameter(ip.getAnnotated().getAnnotation(HttpParam.class).value());
> 
>    }
> }
> {code}
> 
> Producer methods accepting qualifier annotations ensure to have always an annotation instance, this helps to prevent null pointer access since InjectionPoint.getAnnotated().getAnnotation(java.lang.Class<T>) may return null.
> 
> Best regards, Mark
> 
> --
> 
> PALUCH.biz
> Heckenpfad 14 // 69469 Weinheim
> T. 0 62 01/65 04 24-0 // F. 0 62 01/65 04 24-9
> mpaluch at paluch.biz
> http://www.paluch.biz
> 
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev



From issues at jboss.org  Tue Aug  5 08:32:29 2014
From: issues at jboss.org (Mark Paluch (JIRA))
Date: Tue, 5 Aug 2014 08:32:29 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-451) Improve producer method signature
 capability by accepting qualifier annotations
In-Reply-To: <JIRA.12548598.1407241841687@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12548598.1407241841687@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12548598.1407241841687.42604.1407241949497@jira02.app.mwc.hst.phx2.redhat.com>

Mark Paluch created CDI-451:
-------------------------------

             Summary: Improve producer method signature capability by accepting qualifier annotations
                 Key: CDI-451
                 URL: https://issues.jboss.org/browse/CDI-451
             Project: CDI Specification Issues
          Issue Type: Feature Request
          Components: Beans
            Reporter: Mark Paluch
            Priority: Optional


CDI supports producer methods which accept the InjectionPoint as argument which allows to access all metadata to the injection point. The InjectionPoint approach adds a certain complexity which is not needed when only qualifier metadata has to be processed. I propose to allow annotation types within the producer method signatures. Code example for a use case: 

{code}
@HttpParam("username") @Inject String username
{code}

{code}
import javax.enterprise.inject.Produces;
import javax.enterprise.inject.spi.InjectionPoint;

class HttpParams
  @Produces

  String getParamValue(HttpParam httpParam) {

     ServletRequest request = (ServletRequest) FacesContext.getCurrentInstance().getExternalContext().getRequest();
	  
     return request.getParameter(httpParam.value());
	  
     // current support looks like:
     // String getParamValue(InjectionPoint ip) {
     // return request.getParameter(ip.getAnnotated().getAnnotation(HttpParam.class).value());

  }
}
{code}

Producer methods accepting qualifier annotations ensure to have always an annotation instance, this helps to prevent null pointer access since InjectionPoint.getAnnotated().getAnnotation(java.lang.Class<T>) may return null.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)

From issues at jboss.org  Tue Aug 12 06:30:30 2014
From: issues at jboss.org (Jozef Hartinger (JIRA))
Date: Tue, 12 Aug 2014 06:30:30 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-414) Support for "self" injection
In-Reply-To: <JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528622.1388866578000.54892.1407839430338@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/CDI-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992229#comment-12992229 ] 

Jozef Hartinger commented on CDI-414:
-------------------------------------

It is possible if you choose subclassing or bytecode manipulation for interceptors/decorators support. It is not possible if proxies are used to implement interceptors/decorators. Weld uses subclassing.

> Support for "self" injection
> ----------------------------
>
>                 Key: CDI-414
>                 URL: https://issues.jboss.org/browse/CDI-414
>             Project: CDI Specification Issues
>          Issue Type: Bug
>          Components: Resolution
>            Reporter: arjan tijms
>
> Many features of CDI and EJB work by means of a proxy that intercepts calls and adds 'aspects'. In Java it's however not possible to decorate the {{this}} pointer, so methods called on the same bean instance from within a method in the bean do not get their 'aspects' applied.
> This is a well known limitation, but in EJB it's possible to work around this by injecting a bean into itself. E.g.
> {code}
> @Stateless
> public class Foo {
>     @EJB
>     private Foo self;
>     // ...
> }
> {code}
> Also see http://adam-bien.com/roller/abien/entry/how_to_self_invoke_ejb
> Unfortunately using CDI and {{@Inject}} this doesn't work. Weld for instance fails the deployment and logs:
> {noformat}
> WELD-001443 Pseudo scoped bean has circular dependencies.
> {noformat}
> See also: http://adam-bien.com/roller/abien/entry/inject_vs_ejb
> Although there are workarounds, it would be great if {{@Inject}} in combination with CDI could support self injection as well.
> With that projects migrating from {{@EJB}} to {{@Inject}} can do so more easily and the capability can be convenient for new projects as well (e.g. calling two separate {{@Transactional}} methods from a single method without being required to create a new bean).



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)

From jharting at redhat.com  Tue Aug 12 06:42:40 2014
From: jharting at redhat.com (Jozef Hartinger)
Date: Tue, 12 Aug 2014 12:42:40 +0200
Subject: [cdi-dev] Dynamic 'TypeLiteral' with ParameterizedType,
 such as Guice
In-Reply-To: <CAJvqtSp0896tNY+TCkv49PZye1OgNNOacTtAkrBtrU_TGcrjXA@mail.gmail.com>
References: <CAJvqtSp0896tNY+TCkv49PZye1OgNNOacTtAkrBtrU_TGcrjXA@mail.gmail.com>
Message-ID: <53E9EFA0.7090101@redhat.com>

This would be useful not only for bean lookup but also for dispatching 
parameterized events. The only concern is type safety which 
unfortunately cannot be guaranteed (same as in the Guice case). Still, I 
find this useful. Please file a new CDI feature request at 
http://issues.jboss.org/browse/CDI

Jozef

On 08/01/2014 05:51 PM, Luc wrote:
> Hi,
>
> Today I realized about the method 
> 'javax.enterprise.inject.Instance#select(javax.enterprise.util.TypeLiteral, 
> java.lang.annotation.Annotation...)' [1], which whas there from 1.0 
> version.
> After watching CDI 'TypeLiteral' implementation, came a question to 
> mind to me:
>
>   Could be done the same, but *with dynamic class type building*?
>
> And my first google search bring me to a post where a user told some 
> of the benefits of Guice [2] injection and dynamic types [3], which 
> was written at 2010, and it covers exactly my actual needs.
> After watching more the 'TypeLiteral' from CDI and how it is done with 
> Guice, I thought that could be cool to have this feature in CDI too. I 
> know I can do it for my own project (and I will) but I have a few 
> questions:
>
>   * Should I open an issue at CDI Jira? Or is more a Weld issue?
>   * If the issue is open, I'd like to contribute to its development. A 
> part of the "easy rules" from http://www.cdi-spec.org/contribute/, 
> what more should I do?
>
> Thanks!!
>
>   [1]: 
> http://docs.jboss.org/cdi/api/1.0-SP4/javax/enterprise/inject/Instance.html#select(javax.enterprise.util.TypeLiteral 
> <http://docs.jboss.org/cdi/api/1.0-SP4/javax/enterprise/inject/Instance.html#select%28javax.enterprise.util.TypeLiteral>, 
> java.lang.annotation.Annotation...)
>   [2]: https://github.com/google/guice
>   [3]: 
> http://luisfsgoncalves.wordpress.com/2010/09/08/generic-bindings-with-guice/
>
> --
> Lucas
>
>
>
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20140812/7d42fab9/attachment.html 

From issues at jboss.org  Tue Aug 12 07:32:30 2014
From: issues at jboss.org (Antonin Stefanutti (JIRA))
Date: Tue, 12 Aug 2014 07:32:30 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-414) Support for "self" injection
In-Reply-To: <JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528622.1388866578000.55005.1407843150662@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/CDI-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992240#comment-12992240 ] 

Antonin Stefanutti commented on CDI-414:
----------------------------------------

In the [Metrics CDI extension|https://github.com/astefanutti/metrics-cdi], CDI interceptors are used to monitor bean method invocations. In the following use case, I would expect the self-invocation of the annotated method to be intercepted as well:

{code}
import com.codahale.metrics.annotation.Timed;

public class TimedMethodBean {

    @Timed(name = "timedMethod")
    public void timedMethod() {
    }

    public void selfInvocationTimedMethod() {
        timedMethod();
    }
}
{code}

I gave it a try as I knew Weld is using subclassing as proxying technique though it happens that interception of self-invocation bean method isn't working \[1\]. Besides, neither the CDI nor the Java Interceptors specification make that point explicit. The only reference to that question that I've been able to stumble upon is \[2\]:
{quote}
_Method interception_ by interceptors and decorators applies to _business method invocations_ of a simple Web Bean, enterprise Web Bean or EJB bean.
...
Self-invocations of a simple Web Bean are considered to be business method invocations. However, self-invocations of an enterprise Web Bean or EJB session, singleton or message driven bean are not considered to be business method invocations.
{quote}

>From my understanding, valid use cases exist, implementations are capable of supporting it (OWB uses bytecode manipulation \[3\]), yet it has been "disabled" for consistency with EJB which contradicts \[2\]. That'd be valuable to have that cleared explicitly in the upcoming CDI 2.0 specification as Antoine suggested.

\[1\]: https://github.com/astefanutti/metrics-cdi/blob/4625ce1e75b2651935287d1c27964e6af36608a5/envs/se/src/test/java/org/stefanutti/metrics/cdi/se/TimedMethodBeanTest.java#L88
\[2\]: http://docs.jboss.org/webbeans/spec/PDR/html/interceptors.html
\[3\]: https://blogs.apache.org/owb/entry/news_from_openwebbeans_1_2

> Support for "self" injection
> ----------------------------
>
>                 Key: CDI-414
>                 URL: https://issues.jboss.org/browse/CDI-414
>             Project: CDI Specification Issues
>          Issue Type: Bug
>          Components: Resolution
>            Reporter: arjan tijms
>
> Many features of CDI and EJB work by means of a proxy that intercepts calls and adds 'aspects'. In Java it's however not possible to decorate the {{this}} pointer, so methods called on the same bean instance from within a method in the bean do not get their 'aspects' applied.
> This is a well known limitation, but in EJB it's possible to work around this by injecting a bean into itself. E.g.
> {code}
> @Stateless
> public class Foo {
>     @EJB
>     private Foo self;
>     // ...
> }
> {code}
> Also see http://adam-bien.com/roller/abien/entry/how_to_self_invoke_ejb
> Unfortunately using CDI and {{@Inject}} this doesn't work. Weld for instance fails the deployment and logs:
> {noformat}
> WELD-001443 Pseudo scoped bean has circular dependencies.
> {noformat}
> See also: http://adam-bien.com/roller/abien/entry/inject_vs_ejb
> Although there are workarounds, it would be great if {{@Inject}} in combination with CDI could support self injection as well.
> With that projects migrating from {{@EJB}} to {{@Inject}} can do so more easily and the capability can be convenient for new projects as well (e.g. calling two separate {{@Transactional}} methods from a single method without being required to create a new bean).



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)

From issues at jboss.org  Tue Aug 12 07:50:30 2014
From: issues at jboss.org (Jozef Hartinger (JIRA))
Date: Tue, 12 Aug 2014 07:50:30 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-414) Support for "self" injection
In-Reply-To: <JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528622.1388866578000.55060.1407844230991@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/CDI-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992248#comment-12992248 ] 

Jozef Hartinger commented on CDI-414:
-------------------------------------

Yes, Weld does not intercept self invocations. My comment only said that it would be technically possible to support it without much trouble. 

You are quoting an outdated version of the specification. The relevant quotes would be:

{quote}When the application invokes:
? a method of a bean via a contextual reference to the bean, as defined in Section 6.5.3,?Contextual reference for a bean?, or
? a method of a bean via a non-contextual reference to the bean, if the instance was created by the container (e.g. using InjectionTarget.produce() or  UnmanagedInstance.produce()), or
? a business method of a session bean via an EJB remote or local reference, 
the invocation is treated as a *business method invocation*.
{quote}

{quote}If, and only if, an invocation is a *business method invocation* it passes through method interceptors and decorators{quote}

{quote}Otherwise, the invocation is treated as a normal Java method call and is not intercepted by the container.
{quote}

> Support for "self" injection
> ----------------------------
>
>                 Key: CDI-414
>                 URL: https://issues.jboss.org/browse/CDI-414
>             Project: CDI Specification Issues
>          Issue Type: Bug
>          Components: Resolution
>            Reporter: arjan tijms
>
> Many features of CDI and EJB work by means of a proxy that intercepts calls and adds 'aspects'. In Java it's however not possible to decorate the {{this}} pointer, so methods called on the same bean instance from within a method in the bean do not get their 'aspects' applied.
> This is a well known limitation, but in EJB it's possible to work around this by injecting a bean into itself. E.g.
> {code}
> @Stateless
> public class Foo {
>     @EJB
>     private Foo self;
>     // ...
> }
> {code}
> Also see http://adam-bien.com/roller/abien/entry/how_to_self_invoke_ejb
> Unfortunately using CDI and {{@Inject}} this doesn't work. Weld for instance fails the deployment and logs:
> {noformat}
> WELD-001443 Pseudo scoped bean has circular dependencies.
> {noformat}
> See also: http://adam-bien.com/roller/abien/entry/inject_vs_ejb
> Although there are workarounds, it would be great if {{@Inject}} in combination with CDI could support self injection as well.
> With that projects migrating from {{@EJB}} to {{@Inject}} can do so more easily and the capability can be convenient for new projects as well (e.g. calling two separate {{@Transactional}} methods from a single method without being required to create a new bean).



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)


From issues at jboss.org  Tue Aug 12 08:04:30 2014
From: issues at jboss.org (Martin Kouba (JIRA))
Date: Tue, 12 Aug 2014 08:04:30 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-414) Support for "self" injection
In-Reply-To: <JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528622.1388866578000.55087.1407845070510@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/CDI-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992252#comment-12992252 ] 

Martin Kouba commented on CDI-414:
----------------------------------

[~stefanutti] [~jharting] Yep, I believe that example should not work and it's clearly defined by the spec (see also [7.2. Container invocations and interception|http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#biz_method] for the current wording).
{code:java}
public void selfInvocationTimedMethod() { 
        timedMethod(); // <-- this is not a "business method invocation"
}
{code}

> Support for "self" injection
> ----------------------------
>
>                 Key: CDI-414
>                 URL: https://issues.jboss.org/browse/CDI-414
>             Project: CDI Specification Issues
>          Issue Type: Bug
>          Components: Resolution
>            Reporter: arjan tijms
>
> Many features of CDI and EJB work by means of a proxy that intercepts calls and adds 'aspects'. In Java it's however not possible to decorate the {{this}} pointer, so methods called on the same bean instance from within a method in the bean do not get their 'aspects' applied.
> This is a well known limitation, but in EJB it's possible to work around this by injecting a bean into itself. E.g.
> {code}
> @Stateless
> public class Foo {
>     @EJB
>     private Foo self;
>     // ...
> }
> {code}
> Also see http://adam-bien.com/roller/abien/entry/how_to_self_invoke_ejb
> Unfortunately using CDI and {{@Inject}} this doesn't work. Weld for instance fails the deployment and logs:
> {noformat}
> WELD-001443 Pseudo scoped bean has circular dependencies.
> {noformat}
> See also: http://adam-bien.com/roller/abien/entry/inject_vs_ejb
> Although there are workarounds, it would be great if {{@Inject}} in combination with CDI could support self injection as well.
> With that projects migrating from {{@EJB}} to {{@Inject}} can do so more easily and the capability can be convenient for new projects as well (e.g. calling two separate {{@Transactional}} methods from a single method without being required to create a new bean).



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)

From issues at jboss.org  Tue Aug 12 09:36:30 2014
From: issues at jboss.org (Antonin Stefanutti (JIRA))
Date: Tue, 12 Aug 2014 09:36:30 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-414) Support for "self" injection
In-Reply-To: <JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528622.1388866578000.55291.1407850590407@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/CDI-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992284#comment-12992284 ] 

Antonin Stefanutti commented on CDI-414:
----------------------------------------

@[~mkouba], @[~jharting], thanks. Indeed, I agree that, from the CDI specification, self-invocation should not be supported. That being said, from the end-user perspective, the need could be considered legitimate IMO. Though, I understand that the question of self-invocation interception may be more general, that consistency concern with EJB spec for example should be taken into account, and that restrictions on the proxying mechanism chosen by the implementations may not be acceptable.

> Support for "self" injection
> ----------------------------
>
>                 Key: CDI-414
>                 URL: https://issues.jboss.org/browse/CDI-414
>             Project: CDI Specification Issues
>          Issue Type: Bug
>          Components: Resolution
>            Reporter: arjan tijms
>
> Many features of CDI and EJB work by means of a proxy that intercepts calls and adds 'aspects'. In Java it's however not possible to decorate the {{this}} pointer, so methods called on the same bean instance from within a method in the bean do not get their 'aspects' applied.
> This is a well known limitation, but in EJB it's possible to work around this by injecting a bean into itself. E.g.
> {code}
> @Stateless
> public class Foo {
>     @EJB
>     private Foo self;
>     // ...
> }
> {code}
> Also see http://adam-bien.com/roller/abien/entry/how_to_self_invoke_ejb
> Unfortunately using CDI and {{@Inject}} this doesn't work. Weld for instance fails the deployment and logs:
> {noformat}
> WELD-001443 Pseudo scoped bean has circular dependencies.
> {noformat}
> See also: http://adam-bien.com/roller/abien/entry/inject_vs_ejb
> Although there are workarounds, it would be great if {{@Inject}} in combination with CDI could support self injection as well.
> With that projects migrating from {{@EJB}} to {{@Inject}} can do so more easily and the capability can be convenient for new projects as well (e.g. calling two separate {{@Transactional}} methods from a single method without being required to create a new bean).



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)

From issues at jboss.org  Wed Aug 13 16:44:29 2014
From: issues at jboss.org (Ed Burns (JIRA))
Date: Wed, 13 Aug 2014 16:44:29 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-452) Specify that web scoped (request,
 session, application) beans are injectable in async servlets
In-Reply-To: <JIRA.12549310.1407962641087@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12549310.1407962641087@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12549310.1407962641087.58773.1407962669143@jira02.app.mwc.hst.phx2.redhat.com>

Ed Burns created CDI-452:
----------------------------

             Summary: 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


Consider this code based on this blog post: < https://weblogs.java.net/blog/swchan2/archive/2013/06/06/asynchronous-servlet-and-java-ee-concurrency-utilities >.

{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.2.6#6264)

From ajustin at redhat.com  Thu Aug 14 15:55:03 2014
From: ajustin at redhat.com (Ales Justin)
Date: Thu, 14 Aug 2014 21:55:03 +0200
Subject: [cdi-dev] cdi api 1.0 bundle
Message-ID: <2447A2C2-0E99-4E3C-A3C5-9F98716D4ED9@redhat.com>

Any idea where to find the jar/bundle that exports "javax.enterprise.inject"?
(for CDI API 1.0)

This one does, but it's for CDI 1.1 ...
* http://search.maven.org/#artifactdetails%7Cjavax.enterprise%7Ccdi-api%7C1.2%7Cjar

-Ales

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20140814/91e88b55/attachment.html 

From radim.hanus at gmail.com  Thu Aug 14 16:51:58 2014
From: radim.hanus at gmail.com (=?UTF-8?B?UmFkaW0gSGFudcWh?=)
Date: Thu, 14 Aug 2014 22:51:58 +0200
Subject: [cdi-dev] cdi api 1.0 bundle
In-Reply-To: <2447A2C2-0E99-4E3C-A3C5-9F98716D4ED9@redhat.com>
References: <2447A2C2-0E99-4E3C-A3C5-9F98716D4ED9@redhat.com>
Message-ID: <CAFrbYmMuYfuxEh9eGYijPS5Lt=mi+VkKvNCgjd59NG7qeaKymg@mail.gmail.com>

for javaee6/cdi-1.0 applications I used the jboss repository:
https://repository.jboss.org/nexus/content/groups/public-jboss/javax/enterprise/cdi-api/1.0-SP4/

Radim



2014-08-14 21:55 GMT+02:00 Ales Justin <ajustin at redhat.com>:

> Any idea where to find the jar/bundle that exports
> "javax.enterprise.inject"?
> (for CDI API 1.0)
>
> This one does, but it's for CDI 1.1 ...
> *
> http://search.maven.org/#artifactdetails%7Cjavax.enterprise%7Ccdi-api%7C1.2%7Cjar
>
> -Ales
>
>
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20140814/59124934/attachment.html 

From radim.hanus at gmail.com  Thu Aug 14 16:55:32 2014
From: radim.hanus at gmail.com (=?UTF-8?B?UmFkaW0gSGFudcWh?=)
Date: Thu, 14 Aug 2014 22:55:32 +0200
Subject: [cdi-dev] cdi api 1.0 bundle
In-Reply-To: <CAFrbYmMuYfuxEh9eGYijPS5Lt=mi+VkKvNCgjd59NG7qeaKymg@mail.gmail.com>
References: <2447A2C2-0E99-4E3C-A3C5-9F98716D4ED9@redhat.com>
	<CAFrbYmMuYfuxEh9eGYijPS5Lt=mi+VkKvNCgjd59NG7qeaKymg@mail.gmail.com>
Message-ID: <CAFrbYmOw7qMh=HcgHc54QVHmvogQmp6OX3heEK0W=JUAg8bndg@mail.gmail.com>

available in maven central repository as well :)
http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22javax.enterprise%22%20AND%20a%3A%22cdi-api%22

Radim


2014-08-14 22:51 GMT+02:00 Radim Hanu? <radim.hanus at gmail.com>:

> for javaee6/cdi-1.0 applications I used the jboss repository:
>
> https://repository.jboss.org/nexus/content/groups/public-jboss/javax/enterprise/cdi-api/1.0-SP4/
>
> Radim
>
>
>
> 2014-08-14 21:55 GMT+02:00 Ales Justin <ajustin at redhat.com>:
>
>> Any idea where to find the jar/bundle that exports
>> "javax.enterprise.inject"?
>> (for CDI API 1.0)
>>
>> This one does, but it's for CDI 1.1 ...
>> *
>> http://search.maven.org/#artifactdetails%7Cjavax.enterprise%7Ccdi-api%7C1.2%7Cjar
>>
>> -Ales
>>
>>
>> _______________________________________________
>> cdi-dev mailing list
>> cdi-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/cdi-dev
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20140814/8d6c417e/attachment.html 

From ajustin at redhat.com  Thu Aug 14 17:04:33 2014
From: ajustin at redhat.com (Ales Justin)
Date: Thu, 14 Aug 2014 23:04:33 +0200
Subject: [cdi-dev] cdi api 1.0 bundle
In-Reply-To: <CAFrbYmOw7qMh=HcgHc54QVHmvogQmp6OX3heEK0W=JUAg8bndg@mail.gmail.com>
References: <2447A2C2-0E99-4E3C-A3C5-9F98716D4ED9@redhat.com>
	<CAFrbYmMuYfuxEh9eGYijPS5Lt=mi+VkKvNCgjd59NG7qeaKymg@mail.gmail.com>
	<CAFrbYmOw7qMh=HcgHc54QVHmvogQmp6OX3heEK0W=JUAg8bndg@mail.gmail.com>
Message-ID: <9389C25D-33A5-4F52-88DE-BE19FDCB154A@redhat.com>

This one doesn't have OSGi metadata in manifest.mf, but the one from Romain does.
But thanks anyway.

-Ales

On 14 Aug 2014, at 22:55, Radim Hanu? <radim.hanus at gmail.com> wrote:

> available in maven central repository as well :)
> http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22javax.enterprise%22%20AND%20a%3A%22cdi-api%22
> 
> Radim
> 
> 
> 2014-08-14 22:51 GMT+02:00 Radim Hanu? <radim.hanus at gmail.com>:
> for javaee6/cdi-1.0 applications I used the jboss repository: 
> https://repository.jboss.org/nexus/content/groups/public-jboss/javax/enterprise/cdi-api/1.0-SP4/
> 
> Radim
> 
> 
> 
> 2014-08-14 21:55 GMT+02:00 Ales Justin <ajustin at redhat.com>:
> Any idea where to find the jar/bundle that exports "javax.enterprise.inject"?
> (for CDI API 1.0)
> 
> This one does, but it's for CDI 1.1 ...
> * http://search.maven.org/#artifactdetails%7Cjavax.enterprise%7Ccdi-api%7C1.2%7Cjar
> 
> -Ales
> 
> 
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20140814/a701785f/attachment-0001.html 

From struberg at yahoo.de  Sun Aug 17 12:54:47 2014
From: struberg at yahoo.de (Mark Struberg)
Date: Sun, 17 Aug 2014 17:54:47 +0100
Subject: [cdi-dev] cdi api 1.0 bundle
In-Reply-To: <9389C25D-33A5-4F52-88DE-BE19FDCB154A@redhat.com>
Message-ID: <1408294487.75629.YahooMailBasic@web28906.mail.ir2.yahoo.com>

http://repo1.maven.org/maven2/org/apache/geronimo/specs/geronimo-jcdi_1.0_spec/1.0/

does have OSGi metadata ;)

LieGrue,
strub


--------------------------------------------
On Thu, 14/8/14, Ales Justin <ajustin at redhat.com> wrote:

 Subject: Re: [cdi-dev] cdi api 1.0 bundle
 To: cdi-dev at lists.jboss.org
 Date: Thursday, 14 August, 2014, 23:04
 
 This one
 doesn't have OSGi metadata in manifest.mf, but the one
 from Romain does.But thanks anyway.
 -Ales
 On 14 Aug 2014, at 22:55, Radim
 Hanu? <radim.hanus at gmail.com>
 wrote:
 available in maven central
 repository as well :)http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22javax.enterprise%22%20AND%20a%3A%22cdi-api%22
 
 
 Radim
 
 2014-08-14 22:51 GMT+02:00
 Radim Hanu? <radim.hanus at gmail.com>:
 
 for javaee6/cdi-1.0 applications I used the
 jboss repository:?https://repository.jboss.org/nexus/content/groups/public-jboss/javax/enterprise/cdi-api/1.0-SP4/
 
 
 Radim
 
 
 
 2014-08-14 21:55 GMT+02:00
 Ales Justin <ajustin at redhat.com>:
 
 
 Any idea where to find
 the jar/bundle that exports
 "javax.enterprise.inject"?
 
 (for CDI API 1.0)
 This one does, but it's for CDI
 1.1 ...*?http://search.maven.org/#artifactdetails%7Cjavax.enterprise%7Ccdi-api%7C1.2%7Cjar
 
 
 -Ales
 
 _______________________________________________
 
 cdi-dev mailing list
 
 cdi-dev at lists.jboss.org
 
 https://lists.jboss.org/mailman/listinfo/cdi-dev
 
 
 
 
 
 
 -----Inline Attachment Follows-----
 
 _______________________________________________
 cdi-dev mailing list
 cdi-dev at lists.jboss.org
 https://lists.jboss.org/mailman/listinfo/cdi-dev


From issues at jboss.org  Sun Aug 17 13:09:30 2014
From: issues at jboss.org (Mark Struberg (JIRA))
Date: Sun, 17 Aug 2014 13:09:30 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-414) Support for "self" injection
In-Reply-To: <JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528622.1388866578000.62951.1408295370639@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/CDI-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993370#comment-12993370 ] 

Mark Struberg commented on CDI-414:
-----------------------------------

folks, this sounds absolutely like a bug in current Weld. 
The spec clearly defines that invocation of 'business methods' must get intercepted. We had this discussion a long time ago...
See 7.2
{quote}
When the application invokes:
? a method of a bean via a contextual reference to the bean, ...
the invocation is treated as a business method invocation.
{quote}

And this also used to work in older Weld versions. Self injection is a classic pattern which is heavily used in the industry. E.g. if you have a CDI bean which usually returns values from a cache and only on a cache miss it invokes a @Transactional method to fill the cache. If you now tell me that Weld just ignores this @Transactional interceptor then this is *really* bad news. Again, this used to work in older Weld versions...

There is absolutely nothing which we need to change in the spec as this IS already specified.

> Support for "self" injection
> ----------------------------
>
>                 Key: CDI-414
>                 URL: https://issues.jboss.org/browse/CDI-414
>             Project: CDI Specification Issues
>          Issue Type: Bug
>          Components: Resolution
>            Reporter: arjan tijms
>
> Many features of CDI and EJB work by means of a proxy that intercepts calls and adds 'aspects'. In Java it's however not possible to decorate the {{this}} pointer, so methods called on the same bean instance from within a method in the bean do not get their 'aspects' applied.
> This is a well known limitation, but in EJB it's possible to work around this by injecting a bean into itself. E.g.
> {code}
> @Stateless
> public class Foo {
>     @EJB
>     private Foo self;
>     // ...
> }
> {code}
> Also see http://adam-bien.com/roller/abien/entry/how_to_self_invoke_ejb
> Unfortunately using CDI and {{@Inject}} this doesn't work. Weld for instance fails the deployment and logs:
> {noformat}
> WELD-001443 Pseudo scoped bean has circular dependencies.
> {noformat}
> See also: http://adam-bien.com/roller/abien/entry/inject_vs_ejb
> Although there are workarounds, it would be great if {{@Inject}} in combination with CDI could support self injection as well.
> With that projects migrating from {{@EJB}} to {{@Inject}} can do so more easily and the capability can be convenient for new projects as well (e.g. calling two separate {{@Transactional}} methods from a single method without being required to create a new bean).



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)


From issues at jboss.org  Sun Aug 17 13:19:30 2014
From: issues at jboss.org (Mark Struberg (JIRA))
Date: Sun, 17 Aug 2014 13:19:30 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-414) Support for "self" injection
In-Reply-To: <JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528622.1388866578000.62960.1408295970643@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/CDI-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993370#comment-12993370 ] 

Mark Struberg edited comment on CDI-414 at 8/17/14 1:17 PM:
------------------------------------------------------------

folks, this sounds absolutely like a bug in current Weld. 
The spec clearly defines that invocation of 'business methods' must get intercepted. We had this discussion a long time ago...
See 7.2
{quote}
When the application invokes:
? a method of a bean via a contextual reference to the bean, ...
the invocation is treated as a business method invocation.
{quote}

And this also used to work in older Weld versions. Self injection is a classic pattern which is heavily used in the industry. E.g. if you have a CDI bean which usually returns values from a cache and only on a cache miss it invokes a @Transactional method to fill the cache. If you now tell me that Weld just ignores this @Transactional interceptor then this is *really* bad news. Again, this used to work in older Weld versions...

There is absolutely nothing which we need to change in the spec as this IS already specified.

*Edit:*
To make this clear what I' refering to:
* calling a method on a self-injected bean (like in the example from Arjan) _must_ trigger the interceptor. If this doesn't work in Weld, then this is clearly a bug
* calling just another method from the same class (without invoking it via the self-injected Contextual Reference must _not_ trigger the interceptor. This was intended that way.




was (Author: struberg):
folks, this sounds absolutely like a bug in current Weld. 
The spec clearly defines that invocation of 'business methods' must get intercepted. We had this discussion a long time ago...
See 7.2
{quote}
When the application invokes:
? a method of a bean via a contextual reference to the bean, ...
the invocation is treated as a business method invocation.
{quote}

And this also used to work in older Weld versions. Self injection is a classic pattern which is heavily used in the industry. E.g. if you have a CDI bean which usually returns values from a cache and only on a cache miss it invokes a @Transactional method to fill the cache. If you now tell me that Weld just ignores this @Transactional interceptor then this is *really* bad news. Again, this used to work in older Weld versions...

There is absolutely nothing which we need to change in the spec as this IS already specified.

> Support for "self" injection
> ----------------------------
>
>                 Key: CDI-414
>                 URL: https://issues.jboss.org/browse/CDI-414
>             Project: CDI Specification Issues
>          Issue Type: Bug
>          Components: Resolution
>            Reporter: arjan tijms
>
> Many features of CDI and EJB work by means of a proxy that intercepts calls and adds 'aspects'. In Java it's however not possible to decorate the {{this}} pointer, so methods called on the same bean instance from within a method in the bean do not get their 'aspects' applied.
> This is a well known limitation, but in EJB it's possible to work around this by injecting a bean into itself. E.g.
> {code}
> @Stateless
> public class Foo {
>     @EJB
>     private Foo self;
>     // ...
> }
> {code}
> Also see http://adam-bien.com/roller/abien/entry/how_to_self_invoke_ejb
> Unfortunately using CDI and {{@Inject}} this doesn't work. Weld for instance fails the deployment and logs:
> {noformat}
> WELD-001443 Pseudo scoped bean has circular dependencies.
> {noformat}
> See also: http://adam-bien.com/roller/abien/entry/inject_vs_ejb
> Although there are workarounds, it would be great if {{@Inject}} in combination with CDI could support self injection as well.
> With that projects migrating from {{@EJB}} to {{@Inject}} can do so more easily and the capability can be convenient for new projects as well (e.g. calling two separate {{@Transactional}} methods from a single method without being required to create a new bean).



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)


From issues at jboss.org  Mon Aug 18 06:31:30 2014
From: issues at jboss.org (Jozef Hartinger (JIRA))
Date: Mon, 18 Aug 2014 06:31:30 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-414) Support for "self" injection
In-Reply-To: <JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528622.1388866578000.63486.1408357890990@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/CDI-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993436#comment-12993436 ] 

Jozef Hartinger commented on CDI-414:
-------------------------------------

We are talking about *this* invocations which *do not* support interception. This was a reaction to Antoine's suggestion.

> Support for "self" injection
> ----------------------------
>
>                 Key: CDI-414
>                 URL: https://issues.jboss.org/browse/CDI-414
>             Project: CDI Specification Issues
>          Issue Type: Bug
>          Components: Resolution
>            Reporter: arjan tijms
>
> Many features of CDI and EJB work by means of a proxy that intercepts calls and adds 'aspects'. In Java it's however not possible to decorate the {{this}} pointer, so methods called on the same bean instance from within a method in the bean do not get their 'aspects' applied.
> This is a well known limitation, but in EJB it's possible to work around this by injecting a bean into itself. E.g.
> {code}
> @Stateless
> public class Foo {
>     @EJB
>     private Foo self;
>     // ...
> }
> {code}
> Also see http://adam-bien.com/roller/abien/entry/how_to_self_invoke_ejb
> Unfortunately using CDI and {{@Inject}} this doesn't work. Weld for instance fails the deployment and logs:
> {noformat}
> WELD-001443 Pseudo scoped bean has circular dependencies.
> {noformat}
> See also: http://adam-bien.com/roller/abien/entry/inject_vs_ejb
> Although there are workarounds, it would be great if {{@Inject}} in combination with CDI could support self injection as well.
> With that projects migrating from {{@EJB}} to {{@Inject}} can do so more easily and the capability can be convenient for new projects as well (e.g. calling two separate {{@Transactional}} methods from a single method without being required to create a new bean).



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)

From issues at jboss.org  Mon Aug 18 06:33:30 2014
From: issues at jboss.org (Jozef Hartinger (JIRA))
Date: Mon, 18 Aug 2014 06:33:30 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-414) Support for "self" injection
In-Reply-To: <JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528622.1388866578000.63499.1408358010852@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/CDI-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993436#comment-12993436 ] 

Jozef Hartinger edited comment on CDI-414 at 8/18/14 6:32 AM:
--------------------------------------------------------------

We are talking about invocations on {code}this{code} which *do not* support interception. These were reactions to Antoine's suggestion.


was (Author: jharting):
We are talking about *this* invocations which *do not* support interception. This was a reaction to Antoine's suggestion.

> Support for "self" injection
> ----------------------------
>
>                 Key: CDI-414
>                 URL: https://issues.jboss.org/browse/CDI-414
>             Project: CDI Specification Issues
>          Issue Type: Bug
>          Components: Resolution
>            Reporter: arjan tijms
>
> Many features of CDI and EJB work by means of a proxy that intercepts calls and adds 'aspects'. In Java it's however not possible to decorate the {{this}} pointer, so methods called on the same bean instance from within a method in the bean do not get their 'aspects' applied.
> This is a well known limitation, but in EJB it's possible to work around this by injecting a bean into itself. E.g.
> {code}
> @Stateless
> public class Foo {
>     @EJB
>     private Foo self;
>     // ...
> }
> {code}
> Also see http://adam-bien.com/roller/abien/entry/how_to_self_invoke_ejb
> Unfortunately using CDI and {{@Inject}} this doesn't work. Weld for instance fails the deployment and logs:
> {noformat}
> WELD-001443 Pseudo scoped bean has circular dependencies.
> {noformat}
> See also: http://adam-bien.com/roller/abien/entry/inject_vs_ejb
> Although there are workarounds, it would be great if {{@Inject}} in combination with CDI could support self injection as well.
> With that projects migrating from {{@EJB}} to {{@Inject}} can do so more easily and the capability can be convenient for new projects as well (e.g. calling two separate {{@Transactional}} methods from a single method without being required to create a new bean).



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)

From issues at jboss.org  Mon Aug 18 06:39:30 2014
From: issues at jboss.org (Pete Muir (JIRA))
Date: Mon, 18 Aug 2014 06:39:30 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-414) Support for "self" injection
In-Reply-To: <JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528622.1388866578000.63515.1408358370756@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/CDI-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993438#comment-12993438 ] 

Pete Muir commented on CDI-414:
-------------------------------

I'm not sure that injection of "self" dependent scoped beans is required to be supported by the spec. It's probably not a bad idea though.

I agree though that this must work on normal scoped beans as Mark describes.

> Support for "self" injection
> ----------------------------
>
>                 Key: CDI-414
>                 URL: https://issues.jboss.org/browse/CDI-414
>             Project: CDI Specification Issues
>          Issue Type: Bug
>          Components: Resolution
>            Reporter: arjan tijms
>
> Many features of CDI and EJB work by means of a proxy that intercepts calls and adds 'aspects'. In Java it's however not possible to decorate the {{this}} pointer, so methods called on the same bean instance from within a method in the bean do not get their 'aspects' applied.
> This is a well known limitation, but in EJB it's possible to work around this by injecting a bean into itself. E.g.
> {code}
> @Stateless
> public class Foo {
>     @EJB
>     private Foo self;
>     // ...
> }
> {code}
> Also see http://adam-bien.com/roller/abien/entry/how_to_self_invoke_ejb
> Unfortunately using CDI and {{@Inject}} this doesn't work. Weld for instance fails the deployment and logs:
> {noformat}
> WELD-001443 Pseudo scoped bean has circular dependencies.
> {noformat}
> See also: http://adam-bien.com/roller/abien/entry/inject_vs_ejb
> Although there are workarounds, it would be great if {{@Inject}} in combination with CDI could support self injection as well.
> With that projects migrating from {{@EJB}} to {{@Inject}} can do so more easily and the capability can be convenient for new projects as well (e.g. calling two separate {{@Transactional}} methods from a single method without being required to create a new bean).



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)

From issues at jboss.org  Mon Aug 18 14:41:31 2014
From: issues at jboss.org (Mark Struberg (JIRA))
Date: Mon, 18 Aug 2014 14:41:31 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-414) Support for "self" injection
In-Reply-To: <JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528622.1388866578000.64983.1408387291011@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/CDI-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993674#comment-12993674 ] 

Mark Struberg commented on CDI-414:
-----------------------------------

~jharting I was refering to the sample to the original example which (for what I understood) does not work in Weld, but imo this must work according to the spec:

{code}
@ApplicationScoped
public class Foo {

    @Inject
    private Foo self;

    public MyValue getValue() {
      if (!cached) {
        return self.loadValueFromDb();
      }
      return cachedValue;
    }

    @Transactional
    public MyValue loadValueFromDb() {
       return em.....;
    }
}
{code}

Of course just calling this.xxx instead of self.xxx will NOT trigger the interceptor. This is what I already tried to clarify in the *edit* section of my last post.

> Support for "self" injection
> ----------------------------
>
>                 Key: CDI-414
>                 URL: https://issues.jboss.org/browse/CDI-414
>             Project: CDI Specification Issues
>          Issue Type: Bug
>          Components: Resolution
>            Reporter: arjan tijms
>
> Many features of CDI and EJB work by means of a proxy that intercepts calls and adds 'aspects'. In Java it's however not possible to decorate the {{this}} pointer, so methods called on the same bean instance from within a method in the bean do not get their 'aspects' applied.
> This is a well known limitation, but in EJB it's possible to work around this by injecting a bean into itself. E.g.
> {code}
> @Stateless
> public class Foo {
>     @EJB
>     private Foo self;
>     // ...
> }
> {code}
> Also see http://adam-bien.com/roller/abien/entry/how_to_self_invoke_ejb
> Unfortunately using CDI and {{@Inject}} this doesn't work. Weld for instance fails the deployment and logs:
> {noformat}
> WELD-001443 Pseudo scoped bean has circular dependencies.
> {noformat}
> See also: http://adam-bien.com/roller/abien/entry/inject_vs_ejb
> Although there are workarounds, it would be great if {{@Inject}} in combination with CDI could support self injection as well.
> With that projects migrating from {{@EJB}} to {{@Inject}} can do so more easily and the capability can be convenient for new projects as well (e.g. calling two separate {{@Transactional}} methods from a single method without being required to create a new bean).



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)

From issues at jboss.org  Mon Aug 18 14:47:31 2014
From: issues at jboss.org (Mark Struberg (JIRA))
Date: Mon, 18 Aug 2014 14:47:31 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-414) Support for "self" injection
In-Reply-To: <JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528622.1388866578000.65014.1408387651059@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/CDI-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993677#comment-12993677 ] 

Mark Struberg commented on CDI-414:
-----------------------------------

[~pmuir] I also believe that 'self' injecting a @Dependent scoped bean is weird. This currently will most likely lead to an infinite loop I guess. This is also not really limited by the interceptor behaviour but by injection semantics.

But self injecting _normalscoped_ beans is perfectly fine and there should be no difference between injecting the bean into itself or any other bean.

> Support for "self" injection
> ----------------------------
>
>                 Key: CDI-414
>                 URL: https://issues.jboss.org/browse/CDI-414
>             Project: CDI Specification Issues
>          Issue Type: Bug
>          Components: Resolution
>            Reporter: arjan tijms
>
> Many features of CDI and EJB work by means of a proxy that intercepts calls and adds 'aspects'. In Java it's however not possible to decorate the {{this}} pointer, so methods called on the same bean instance from within a method in the bean do not get their 'aspects' applied.
> This is a well known limitation, but in EJB it's possible to work around this by injecting a bean into itself. E.g.
> {code}
> @Stateless
> public class Foo {
>     @EJB
>     private Foo self;
>     // ...
> }
> {code}
> Also see http://adam-bien.com/roller/abien/entry/how_to_self_invoke_ejb
> Unfortunately using CDI and {{@Inject}} this doesn't work. Weld for instance fails the deployment and logs:
> {noformat}
> WELD-001443 Pseudo scoped bean has circular dependencies.
> {noformat}
> See also: http://adam-bien.com/roller/abien/entry/inject_vs_ejb
> Although there are workarounds, it would be great if {{@Inject}} in combination with CDI could support self injection as well.
> With that projects migrating from {{@EJB}} to {{@Inject}} can do so more easily and the capability can be convenient for new projects as well (e.g. calling two separate {{@Transactional}} methods from a single method without being required to create a new bean).



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)

From issues at jboss.org  Mon Aug 18 14:49:29 2014
From: issues at jboss.org (Arne Limburg (JIRA))
Date: Mon, 18 Aug 2014 14:49:29 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-414) Support for "self" injection
In-Reply-To: <JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528622.1388866578000.65016.1408387769807@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/CDI-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993678#comment-12993678 ] 

Arne Limburg commented on CDI-414:
----------------------------------

Mark, your example does work in weld, as I understand. The initial example was talking about @Dependent beans. We could clarify in the spec, that self-injection of pseudo-scoped beans has to work for everything except constructor-injection. Therefor we have the differentiation of Producer#produce and InjectionTarget#inject. And we could clarify the behavior for constructor-self-injection (OWB has a StackOverflowError then, I think).

> Support for "self" injection
> ----------------------------
>
>                 Key: CDI-414
>                 URL: https://issues.jboss.org/browse/CDI-414
>             Project: CDI Specification Issues
>          Issue Type: Bug
>          Components: Resolution
>            Reporter: arjan tijms
>
> Many features of CDI and EJB work by means of a proxy that intercepts calls and adds 'aspects'. In Java it's however not possible to decorate the {{this}} pointer, so methods called on the same bean instance from within a method in the bean do not get their 'aspects' applied.
> This is a well known limitation, but in EJB it's possible to work around this by injecting a bean into itself. E.g.
> {code}
> @Stateless
> public class Foo {
>     @EJB
>     private Foo self;
>     // ...
> }
> {code}
> Also see http://adam-bien.com/roller/abien/entry/how_to_self_invoke_ejb
> Unfortunately using CDI and {{@Inject}} this doesn't work. Weld for instance fails the deployment and logs:
> {noformat}
> WELD-001443 Pseudo scoped bean has circular dependencies.
> {noformat}
> See also: http://adam-bien.com/roller/abien/entry/inject_vs_ejb
> Although there are workarounds, it would be great if {{@Inject}} in combination with CDI could support self injection as well.
> With that projects migrating from {{@EJB}} to {{@Inject}} can do so more easily and the capability can be convenient for new projects as well (e.g. calling two separate {{@Transactional}} methods from a single method without being required to create a new bean).



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)

From issues at jboss.org  Mon Aug 18 14:57:30 2014
From: issues at jboss.org (Mark Struberg (JIRA))
Date: Mon, 18 Aug 2014 14:57:30 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-414) Support for "self" injection
In-Reply-To: <JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528622.1388866578000.65047.1408388250632@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/CDI-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993685#comment-12993685 ] 

Mark Struberg commented on CDI-414:
-----------------------------------

Oh, I did not look at the error message but only at Arjans comment

{quote}
Unfortunately using CDI and @Inject this doesn't work. Weld for instance fails the deployment and logs
{quote}

Of course, with @Dependent scoped beans it will fail because of cyclic injection. If it works for any @NormalScoped beans in Weld, then all is fine!.
In that case I don't think we need to clarify anything. It's perfectly clear from the current spec that cyclic dependencies of @Dependent scoped beans is intentionally not supported.

> Support for "self" injection
> ----------------------------
>
>                 Key: CDI-414
>                 URL: https://issues.jboss.org/browse/CDI-414
>             Project: CDI Specification Issues
>          Issue Type: Bug
>          Components: Resolution
>            Reporter: arjan tijms
>
> Many features of CDI and EJB work by means of a proxy that intercepts calls and adds 'aspects'. In Java it's however not possible to decorate the {{this}} pointer, so methods called on the same bean instance from within a method in the bean do not get their 'aspects' applied.
> This is a well known limitation, but in EJB it's possible to work around this by injecting a bean into itself. E.g.
> {code}
> @Stateless
> public class Foo {
>     @EJB
>     private Foo self;
>     // ...
> }
> {code}
> Also see http://adam-bien.com/roller/abien/entry/how_to_self_invoke_ejb
> Unfortunately using CDI and {{@Inject}} this doesn't work. Weld for instance fails the deployment and logs:
> {noformat}
> WELD-001443 Pseudo scoped bean has circular dependencies.
> {noformat}
> See also: http://adam-bien.com/roller/abien/entry/inject_vs_ejb
> Although there are workarounds, it would be great if {{@Inject}} in combination with CDI could support self injection as well.
> With that projects migrating from {{@EJB}} to {{@Inject}} can do so more easily and the capability can be convenient for new projects as well (e.g. calling two separate {{@Transactional}} methods from a single method without being required to create a new bean).



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)

From issues at jboss.org  Tue Aug 19 08:51:32 2014
From: issues at jboss.org (Antonio Goncalves (JIRA))
Date: Tue, 19 Aug 2014 08:51:32 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-4) Need a way to provide ordering for
 Event observers
In-Reply-To: <JIRA.12415300.1280185626000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12415300.1280185626000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12415300.1280185626000.66772.1408452692926@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/CDI-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993903#comment-12993903 ] 

Antonio Goncalves commented on CDI-4:
-------------------------------------

And now that we have {{@Priority}}, can't we just use it ?

{code}
public class MyBean
	public void myFirstObserverInPriority(@Observes @Priority(1000) MyEvent event) { ... }
}

public class MyBean
	public void mySecondObserverInPriority(@Observes @Priority(42) MyEvent event) { ... }
}
{code}


> Need a way to provide ordering for Event observers
> --------------------------------------------------
>
>                 Key: CDI-4
>                 URL: https://issues.jboss.org/browse/CDI-4
>             Project: CDI Specification Issues
>          Issue Type: Feature Request
>          Components: Events, Portable Extensions
>    Affects Versions: 1.0
>         Environment: All
>            Reporter: Lincoln Baxter III
>            Assignee: Pete Muir
>             Fix For: 2.0 (discussion)
>
>
> There needs to be a way to specify some kind of ordering for Event observers. 
> Understandably, this is somewhat counter-intuitive to the general concept of observing an event, but there is going to be need for this in an upcoming JBoss project. While it can be done manually, it might be nice to have a built-in API.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)

From issues at jboss.org  Tue Aug 19 09:15:37 2014
From: issues at jboss.org (Antonio Goncalves (JIRA))
Date: Tue, 19 Aug 2014 09:15:37 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-25) Support @Inject FacesContext
	facesContext; 
In-Reply-To: <JIRA.12427721.1294673571000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12427721.1294673571000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12427721.1294673571000.66822.1408454137167@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/CDI-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993909#comment-12993909 ] 

Antonio Goncalves commented on CDI-25:
--------------------------------------

See [https://java.net/jira/browse/JAVASERVERFACES_SPEC_PUBLIC-527]

> Support @Inject FacesContext facesContext;
> ------------------------------------------
>
>                 Key: CDI-25
>                 URL: https://issues.jboss.org/browse/CDI-25
>             Project: CDI Specification Issues
>          Issue Type: Feature Request
>          Components: Java EE integration
>    Affects Versions: 1.0
>            Reporter: Pete Muir
>             Fix For: TBD
>
>




--
This message was sent by Atlassian JIRA
(v6.2.6#6264)

From issues at jboss.org  Tue Aug 19 09:51:31 2014
From: issues at jboss.org (Antonio Goncalves (JIRA))
Date: Tue, 19 Aug 2014 09:51:31 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-414) Support for "self" injection
In-Reply-To: <JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528622.1388866578000.67029.1408456291237@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/CDI-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12993936#comment-12993936 ] 

Antonio Goncalves commented on CDI-414:
---------------------------------------

Inner call AOP was a topic discussed at JavaOne 2013 with Marina Vatkina (spec lead of Interceptor 1.2). Inner calls AOP are not possible in Java EE and to add it in a consistent manner, this functionnality should be added to the Interceptor spec (https://java.net/jira/browse/INTERCEPTORS_SPEC)

> Support for "self" injection
> ----------------------------
>
>                 Key: CDI-414
>                 URL: https://issues.jboss.org/browse/CDI-414
>             Project: CDI Specification Issues
>          Issue Type: Bug
>          Components: Resolution
>            Reporter: arjan tijms
>
> Many features of CDI and EJB work by means of a proxy that intercepts calls and adds 'aspects'. In Java it's however not possible to decorate the {{this}} pointer, so methods called on the same bean instance from within a method in the bean do not get their 'aspects' applied.
> This is a well known limitation, but in EJB it's possible to work around this by injecting a bean into itself. E.g.
> {code}
> @Stateless
> public class Foo {
>     @EJB
>     private Foo self;
>     // ...
> }
> {code}
> Also see http://adam-bien.com/roller/abien/entry/how_to_self_invoke_ejb
> Unfortunately using CDI and {{@Inject}} this doesn't work. Weld for instance fails the deployment and logs:
> {noformat}
> WELD-001443 Pseudo scoped bean has circular dependencies.
> {noformat}
> See also: http://adam-bien.com/roller/abien/entry/inject_vs_ejb
> Although there are workarounds, it would be great if {{@Inject}} in combination with CDI could support self injection as well.
> With that projects migrating from {{@EJB}} to {{@Inject}} can do so more easily and the capability can be convenient for new projects as well (e.g. calling two separate {{@Transactional}} methods from a single method without being required to create a new bean).



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)

From issues at jboss.org  Tue Aug 19 17:01:30 2014
From: issues at jboss.org (arjan tijms (JIRA))
Date: Tue, 19 Aug 2014 17:01:30 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-414) Support for "self" injection
In-Reply-To: <JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528622.1388866578000.67982.1408482090820@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/CDI-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12994111#comment-12994111 ] 

arjan tijms commented on CDI-414:
---------------------------------

{quote}Which scope are you using?{quote}

For the specific case as given in the original example: no explicit scope. Just a {{stateless}} EJB into itself:

{code}
@Stateless
public class Foo {

    @EJB
    private Foo self;

    // ...
}
{code}

As stated, this works when using {{@EJB}}, but does not work when using {{@Inject}}, so for this particular use case injecting via {{@EJB}} is more powerful in a way, since it's capable of doing a kind of injection that CDI currently can not do.

Maybe another solution is to define a CDI scope (or something else) that closely mimics EJB's {{@Stateless}} and for which self-injection is explicitly supported.

> Support for "self" injection
> ----------------------------
>
>                 Key: CDI-414
>                 URL: https://issues.jboss.org/browse/CDI-414
>             Project: CDI Specification Issues
>          Issue Type: Bug
>          Components: Resolution
>            Reporter: arjan tijms
>
> Many features of CDI and EJB work by means of a proxy that intercepts calls and adds 'aspects'. In Java it's however not possible to decorate the {{this}} pointer, so methods called on the same bean instance from within a method in the bean do not get their 'aspects' applied.
> This is a well known limitation, but in EJB it's possible to work around this by injecting a bean into itself. E.g.
> {code}
> @Stateless
> public class Foo {
>     @EJB
>     private Foo self;
>     // ...
> }
> {code}
> Also see http://adam-bien.com/roller/abien/entry/how_to_self_invoke_ejb
> Unfortunately using CDI and {{@Inject}} this doesn't work. Weld for instance fails the deployment and logs:
> {noformat}
> WELD-001443 Pseudo scoped bean has circular dependencies.
> {noformat}
> See also: http://adam-bien.com/roller/abien/entry/inject_vs_ejb
> Although there are workarounds, it would be great if {{@Inject}} in combination with CDI could support self injection as well.
> With that projects migrating from {{@EJB}} to {{@Inject}} can do so more easily and the capability can be convenient for new projects as well (e.g. calling two separate {{@Transactional}} methods from a single method without being required to create a new bean).



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)

From issues at jboss.org  Wed Aug 20 02:33:30 2014
From: issues at jboss.org (Mark Struberg (JIRA))
Date: Wed, 20 Aug 2014 02:33:30 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-414) Support for "self" injection
In-Reply-To: <JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528622.1388866578000.68215.1408516410852@jira02.app.mwc.hst.phx2.redhat.com>


    [ https://issues.jboss.org/browse/CDI-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12994157#comment-12994157 ] 

Mark Struberg commented on CDI-414:
-----------------------------------

[~atijms] Ok, I thought your EJB code was only an example about how it works within pure EJBs. 
Of course @Inject in @Stateless beans should work the same way as @EJB. It actually should really make no difference if you resolve the EJB via @Inject, @EJB or manually from JNDI. If this doesn't work it is a bug imo. 

But this most likely has nothing to do with Weld but more with the integration in the EJB container. What JavaEE server did you have this problem with?

> Support for "self" injection
> ----------------------------
>
>                 Key: CDI-414
>                 URL: https://issues.jboss.org/browse/CDI-414
>             Project: CDI Specification Issues
>          Issue Type: Bug
>          Components: Resolution
>            Reporter: arjan tijms
>
> Many features of CDI and EJB work by means of a proxy that intercepts calls and adds 'aspects'. In Java it's however not possible to decorate the {{this}} pointer, so methods called on the same bean instance from within a method in the bean do not get their 'aspects' applied.
> This is a well known limitation, but in EJB it's possible to work around this by injecting a bean into itself. E.g.
> {code}
> @Stateless
> public class Foo {
>     @EJB
>     private Foo self;
>     // ...
> }
> {code}
> Also see http://adam-bien.com/roller/abien/entry/how_to_self_invoke_ejb
> Unfortunately using CDI and {{@Inject}} this doesn't work. Weld for instance fails the deployment and logs:
> {noformat}
> WELD-001443 Pseudo scoped bean has circular dependencies.
> {noformat}
> See also: http://adam-bien.com/roller/abien/entry/inject_vs_ejb
> Although there are workarounds, it would be great if {{@Inject}} in combination with CDI could support self injection as well.
> With that projects migrating from {{@EJB}} to {{@Inject}} can do so more easily and the capability can be convenient for new projects as well (e.g. calling two separate {{@Transactional}} methods from a single method without being required to create a new bean).



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)

From issues at jboss.org  Wed Aug 20 10:09:32 2014
From: issues at jboss.org (Jozef Hartinger (JIRA))
Date: Wed, 20 Aug 2014 10:09:32 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-414) Support for "self" injection
In-Reply-To: <JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528622.1388866578000.69741.1408543772164@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/CDI-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jozef Hartinger reassigned CDI-414:
-----------------------------------

    Assignee: Jozef Hartinger


> Support for "self" injection
> ----------------------------
>
>                 Key: CDI-414
>                 URL: https://issues.jboss.org/browse/CDI-414
>             Project: CDI Specification Issues
>          Issue Type: Bug
>          Components: Resolution
>            Reporter: arjan tijms
>            Assignee: Jozef Hartinger
>
> Many features of CDI and EJB work by means of a proxy that intercepts calls and adds 'aspects'. In Java it's however not possible to decorate the {{this}} pointer, so methods called on the same bean instance from within a method in the bean do not get their 'aspects' applied.
> This is a well known limitation, but in EJB it's possible to work around this by injecting a bean into itself. E.g.
> {code}
> @Stateless
> public class Foo {
>     @EJB
>     private Foo self;
>     // ...
> }
> {code}
> Also see http://adam-bien.com/roller/abien/entry/how_to_self_invoke_ejb
> Unfortunately using CDI and {{@Inject}} this doesn't work. Weld for instance fails the deployment and logs:
> {noformat}
> WELD-001443 Pseudo scoped bean has circular dependencies.
> {noformat}
> See also: http://adam-bien.com/roller/abien/entry/inject_vs_ejb
> Although there are workarounds, it would be great if {{@Inject}} in combination with CDI could support self injection as well.
> With that projects migrating from {{@EJB}} to {{@Inject}} can do so more easily and the capability can be convenient for new projects as well (e.g. calling two separate {{@Transactional}} methods from a single method without being required to create a new bean).



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)

From issues at jboss.org  Wed Aug 20 10:55:31 2014
From: issues at jboss.org (Jozef Hartinger (JIRA))
Date: Wed, 20 Aug 2014 10:55:31 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-414) Support for "self" injection
In-Reply-To: <JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
References: <JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528622.1388866578000.69976.1408546531234@jira02.app.mwc.hst.phx2.redhat.com>


     [ https://issues.jboss.org/browse/CDI-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jozef Hartinger reassigned CDI-414:
-----------------------------------

    Assignee:     (was: Jozef Hartinger)


> Support for "self" injection
> ----------------------------
>
>                 Key: CDI-414
>                 URL: https://issues.jboss.org/browse/CDI-414
>             Project: CDI Specification Issues
>          Issue Type: Bug
>          Components: Resolution
>            Reporter: arjan tijms
>
> Many features of CDI and EJB work by means of a proxy that intercepts calls and adds 'aspects'. In Java it's however not possible to decorate the {{this}} pointer, so methods called on the same bean instance from within a method in the bean do not get their 'aspects' applied.
> This is a well known limitation, but in EJB it's possible to work around this by injecting a bean into itself. E.g.
> {code}
> @Stateless
> public class Foo {
>     @EJB
>     private Foo self;
>     // ...
> }
> {code}
> Also see http://adam-bien.com/roller/abien/entry/how_to_self_invoke_ejb
> Unfortunately using CDI and {{@Inject}} this doesn't work. Weld for instance fails the deployment and logs:
> {noformat}
> WELD-001443 Pseudo scoped bean has circular dependencies.
> {noformat}
> See also: http://adam-bien.com/roller/abien/entry/inject_vs_ejb
> Although there are workarounds, it would be great if {{@Inject}} in combination with CDI could support self injection as well.
> With that projects migrating from {{@EJB}} to {{@Inject}} can do so more easily and the capability can be convenient for new projects as well (e.g. calling two separate {{@Transactional}} methods from a single method without being required to create a new bean).



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)

From john.d.ament at gmail.com  Thu Aug 21 14:43:13 2014
From: john.d.ament at gmail.com (John D. Ament)
Date: Thu, 21 Aug 2014 14:43:13 -0400
Subject: [cdi-dev] Interceptor scopes
Message-ID: <CAOqetn-CF2mHTodOd03b9H1KTmHfSgSjNcphthiGg+RX7SkhwQ@mail.gmail.com>

Hi,

Let's suppose I'm deploying a WAR file w/ multiple JAR files.  The WAR has
a beans.xml w/ interceptors defined in it.  The JARs each have beans.xml,
but no interceptors defined within them.

Should the interceptors in the WAR apply to all of the JAR files?

Thanks,

John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20140821/5ef5dbbd/attachment.html 

From jharting at redhat.com  Fri Aug 22 05:10:40 2014
From: jharting at redhat.com (Jozef Hartinger)
Date: Fri, 22 Aug 2014 11:10:40 +0200
Subject: [cdi-dev] Interceptor scopes
In-Reply-To: <CAOqetn-CF2mHTodOd03b9H1KTmHfSgSjNcphthiGg+RX7SkhwQ@mail.gmail.com>
References: <CAOqetn-CF2mHTodOd03b9H1KTmHfSgSjNcphthiGg+RX7SkhwQ@mail.gmail.com>
Message-ID: <53F70910.5010005@redhat.com>

Hi John,

no, the interceptor will only be enabled in war's WEB-INF/classes. Other 
JARs need to enable the interceptor in their beans.xml file to use it.

Jozef

On 08/21/2014 08:43 PM, John D. Ament wrote:
> Hi,
>
> Let's suppose I'm deploying a WAR file w/ multiple JAR files.  The WAR 
> has a beans.xml w/ interceptors defined in it.  The JARs each have 
> beans.xml, but no interceptors defined within them.
>
> Should the interceptors in the WAR apply to all of the JAR files?
>
> Thanks,
>
> John
>
>
>
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20140822/1fd9bdad/attachment.html 

From rmannibucau at gmail.com  Fri Aug 22 07:05:44 2014
From: rmannibucau at gmail.com (Romain Manni-Bucau)
Date: Fri, 22 Aug 2014 13:05:44 +0200
Subject: [cdi-dev] Interceptor scopes
In-Reply-To: <53F70910.5010005@redhat.com>
References: <CAOqetn-CF2mHTodOd03b9H1KTmHfSgSjNcphthiGg+RX7SkhwQ@mail.gmail.com>
	<53F70910.5010005@redhat.com>
Message-ID: <CACLE=7OuLR800yM0ELYoQfkN8b2MVm-FcTESociyY5G2U1Nf5w@mail.gmail.com>

Hi John, from spec point of view Jozef is right but I think it is
important to mention that most of servers supports it otherwise it is
hardly usable (using lib would be a nightmare).


Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
LinkedIn: http://fr.linkedin.com/in/rmannibucau
Github: https://github.com/rmannibucau


2014-08-22 11:10 GMT+02:00 Jozef Hartinger <jharting at redhat.com>:
> Hi John,
>
> no, the interceptor will only be enabled in war's WEB-INF/classes. Other
> JARs need to enable the interceptor in their beans.xml file to use it.
>
> Jozef
>
>
> On 08/21/2014 08:43 PM, John D. Ament wrote:
>
> Hi,
>
> Let's suppose I'm deploying a WAR file w/ multiple JAR files.  The WAR has a
> beans.xml w/ interceptors defined in it.  The JARs each have beans.xml, but
> no interceptors defined within them.
>
> Should the interceptors in the WAR apply to all of the JAR files?
>
> Thanks,
>
> John
>
>
>
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev
>
>
>
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev

From john.d.ament at gmail.com  Fri Aug 22 07:21:39 2014
From: john.d.ament at gmail.com (John D. Ament)
Date: Fri, 22 Aug 2014 07:21:39 -0400
Subject: [cdi-dev] Interceptor scopes
In-Reply-To: <CACLE=7OuLR800yM0ELYoQfkN8b2MVm-FcTESociyY5G2U1Nf5w@mail.gmail.com>
References: <CAOqetn-CF2mHTodOd03b9H1KTmHfSgSjNcphthiGg+RX7SkhwQ@mail.gmail.com>
	<53F70910.5010005@redhat.com>
	<CACLE=7OuLR800yM0ELYoQfkN8b2MVm-FcTESociyY5G2U1Nf5w@mail.gmail.com>
Message-ID: <CAOqetn__yoc9e2s3NMzp+ZSwVEAP0TxZxbTV39NeQBKcULCUmQ@mail.gmail.com>

@Romain

I'm inclined to believe that.  Either way I just created
https://issues.jboss.org/browse/CDI-453 so that none of us lose track of it.

John


On Fri, Aug 22, 2014 at 7:05 AM, Romain Manni-Bucau <rmannibucau at gmail.com>
wrote:

> Hi John, from spec point of view Jozef is right but I think it is
> important to mention that most of servers supports it otherwise it is
> hardly usable (using lib would be a nightmare).
>
>
> Romain Manni-Bucau
> Twitter: @rmannibucau
> Blog: http://rmannibucau.wordpress.com/
> LinkedIn: http://fr.linkedin.com/in/rmannibucau
> Github: https://github.com/rmannibucau
>
>
> 2014-08-22 11:10 GMT+02:00 Jozef Hartinger <jharting at redhat.com>:
> > Hi John,
> >
> > no, the interceptor will only be enabled in war's WEB-INF/classes. Other
> > JARs need to enable the interceptor in their beans.xml file to use it.
> >
> > Jozef
> >
> >
> > On 08/21/2014 08:43 PM, John D. Ament wrote:
> >
> > Hi,
> >
> > Let's suppose I'm deploying a WAR file w/ multiple JAR files.  The WAR
> has a
> > beans.xml w/ interceptors defined in it.  The JARs each have beans.xml,
> but
> > no interceptors defined within them.
> >
> > Should the interceptors in the WAR apply to all of the JAR files?
> >
> > Thanks,
> >
> > John
> >
> >
> >
> > _______________________________________________
> > cdi-dev mailing list
> > cdi-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/cdi-dev
> >
> >
> >
> > _______________________________________________
> > cdi-dev mailing list
> > cdi-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/cdi-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20140822/f6886dbd/attachment.html 

From issues at jboss.org  Fri Aug 22 07:21:59 2014
From: issues at jboss.org (John Ament (JIRA))
Date: Fri, 22 Aug 2014 07:21:59 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-453) Support for external interceptor
 configuration
In-Reply-To: <JIRA.12550007.1408706462000@Atlassian.JIRA>
References: <JIRA.12550007.1408706462000@Atlassian.JIRA>
	<JIRA.12550007.1408706462206@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12550007.1408706462000.2277.1408706519527@Atlassian.JIRA>

John Ament created CDI-453:
------------------------------

             Summary: Support for external interceptor configuration
                 Key: CDI-453
                 URL: https://issues.jboss.org/browse/CDI-453
             Project: CDI Specification Issues
          Issue Type: Feature Request
          Components: Interceptors, Java EE integration, Java SE Integration
    Affects Versions: 1.2.Final
            Reporter: John Ament
            Priority: Minor


Currently, there is no way to flag that an interceptor should be globally enabled/disabled within an archive/application.

Say that I have a common JAR with some interceptor annotations on various beans within it.  This JAR has two targetted runtimes, one in a servlet/app server runtime where in one interceptor should be enabled and another disabled.  This same JAR is also used within a standalone (SE) batch program where the first interceptor is off and the second is on.

In this case, I need a way to specify that an interceptor is on, without changing the deployed bean archive.  I can currently alleviate this through maven shading, but would prefer not to since it tightly couples the archive to the way consumers use it.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Fri Aug 22 07:28:59 2014
From: issues at jboss.org (Romain Manni-Bucau (JIRA))
Date: Fri, 22 Aug 2014 07:28:59 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-453) Support for external interceptor
 configuration
In-Reply-To: <JIRA.12550007.1408706462000@Atlassian.JIRA>
References: <JIRA.12550007.1408706462000@Atlassian.JIRA>
	<JIRA.12550007.1408706462000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12550007.1408706462000.2290.1408706939702@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/CDI-453?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995022#comment-12995022 ] 

Romain Manni-Bucau commented on CDI-453:
----------------------------------------

+1

snice most of servers consider it as global by default we should consider having it as default and allowing only to restrict an interceptor to a bean archive (in <interceptor /> we can add an attribute restricted=true|false)

> Support for external interceptor configuration
> ----------------------------------------------
>
>                 Key: CDI-453
>                 URL: https://issues.jboss.org/browse/CDI-453
>             Project: CDI Specification Issues
>          Issue Type: Feature Request
>          Components: Interceptors, Java EE integration, Java SE Integration
>    Affects Versions: 1.2.Final
>            Reporter: John Ament
>            Priority: Minor
>
> Currently, there is no way to flag that an interceptor should be globally enabled/disabled within an archive/application.
> Say that I have a common JAR with some interceptor annotations on various beans within it.  This JAR has two targetted runtimes, one in a servlet/app server runtime where in one interceptor should be enabled and another disabled.  This same JAR is also used within a standalone (SE) batch program where the first interceptor is off and the second is on.
> In this case, I need a way to specify that an interceptor is on, without changing the deployed bean archive.  I can currently alleviate this through maven shading, but would prefer not to since it tightly couples the archive to the way consumers use it.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From struberg at yahoo.de  Sat Aug 23 04:36:32 2014
From: struberg at yahoo.de (Mark Struberg)
Date: Sat, 23 Aug 2014 09:36:32 +0100
Subject: [cdi-dev] Interceptor scopes
In-Reply-To: <CAOqetn__yoc9e2s3NMzp+ZSwVEAP0TxZxbTV39NeQBKcULCUmQ@mail.gmail.com>
References: <CAOqetn-CF2mHTodOd03b9H1KTmHfSgSjNcphthiGg+RX7SkhwQ@mail.gmail.com>	<53F70910.5010005@redhat.com>	<CACLE=7OuLR800yM0ELYoQfkN8b2MVm-FcTESociyY5G2U1Nf5w@mail.gmail.com>
	<CAOqetn__yoc9e2s3NMzp+ZSwVEAP0TxZxbTV39NeQBKcULCUmQ@mail.gmail.com>
Message-ID: <1408782992.38627.YahooMailNeo@web28904.mail.ir2.yahoo.com>

I don't believe this is clearly defined in the spec.
See https://issues.jboss.org/browse/CDI-129 and the discussion in CDI-18 as well.

EARs are in general just frigging broken/underspecified. But this is actually not (only) a CDI issue but a result of the missing isolation/Classloader behaviour specification in the EE umbrella spec.


LieGrue,
strub



On Friday, 22 August 2014, 13:22, John D. Ament <john.d.ament at gmail.com> wrote:
 

>
>
>@Romain
>
>
>I'm inclined to believe that. ?Either way I just created?https://issues.jboss.org/browse/CDI-453 so that none of us lose track of it.
>
>
>John
>
>
>
>On Fri, Aug 22, 2014 at 7:05 AM, Romain Manni-Bucau <rmannibucau at gmail.com> wrote:
>
>Hi John, from spec point of view Jozef is right but I think it is
>>important to mention that most of servers supports it otherwise it is
>>hardly usable (using lib would be a nightmare).
>>
>>
>>Romain Manni-Bucau
>>Twitter: @rmannibucau
>>Blog: http://rmannibucau.wordpress.com/
>>LinkedIn: http://fr.linkedin.com/in/rmannibucau
>>Github: https://github.com/rmannibucau
>>
>>
>>2014-08-22 11:10 GMT+02:00 Jozef Hartinger <jharting at redhat.com>:
>>
>>> Hi John,
>>>
>>> no, the interceptor will only be enabled in war's WEB-INF/classes. Other
>>> JARs need to enable the interceptor in their beans.xml file to use it.
>>>
>>> Jozef
>>>
>>>
>>> On 08/21/2014 08:43 PM, John D. Ament wrote:
>>>
>>> Hi,
>>>
>>> Let's suppose I'm deploying a WAR file w/ multiple JAR files.? The WAR has a
>>> beans.xml w/ interceptors defined in it.? The JARs each have beans.xml, but
>>> no interceptors defined within them.
>>>
>>> Should the interceptors in the WAR apply to all of the JAR files?
>>>
>>> Thanks,
>>>
>>> John
>>>
>>>
>>>
>>> _______________________________________________
>>> cdi-dev mailing list
>>> cdi-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/cdi-dev
>>>
>>>
>>>
>>> _______________________________________________
>>> cdi-dev mailing list
>>> cdi-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/cdi-dev
>>
>
>
>_______________________________________________
>cdi-dev mailing list
>cdi-dev at lists.jboss.org
>https://lists.jboss.org/mailman/listinfo/cdi-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20140823/4320ad76/attachment.html 

From jharting at redhat.com  Sat Aug 23 11:43:23 2014
From: jharting at redhat.com (Jozef Hartinger)
Date: Sat, 23 Aug 2014 17:43:23 +0200
Subject: [cdi-dev] Interceptor scopes
In-Reply-To: <CAOqetn__yoc9e2s3NMzp+ZSwVEAP0TxZxbTV39NeQBKcULCUmQ@mail.gmail.com>
References: <CAOqetn-CF2mHTodOd03b9H1KTmHfSgSjNcphthiGg+RX7SkhwQ@mail.gmail.com>	<53F70910.5010005@redhat.com>	<CACLE=7OuLR800yM0ELYoQfkN8b2MVm-FcTESociyY5G2U1Nf5w@mail.gmail.com>
	<CAOqetn__yoc9e2s3NMzp+ZSwVEAP0TxZxbTV39NeQBKcULCUmQ@mail.gmail.com>
Message-ID: <53F8B69B.2040702@redhat.com>

Since CDI 1.1 you can enable an interceptor, decorator or alternative 
globally. This can be done either using the @Priority annotation or by 
an extension.

Jozef

On 08/22/2014 01:21 PM, John D. Ament wrote:
> @Romain
>
> I'm inclined to believe that.  Either way I just created 
> https://issues.jboss.org/browse/CDI-453 so that none of us lose track 
> of it.
>
> John
>
>
> On Fri, Aug 22, 2014 at 7:05 AM, Romain Manni-Bucau 
> <rmannibucau at gmail.com <mailto:rmannibucau at gmail.com>> wrote:
>
>     Hi John, from spec point of view Jozef is right but I think it is
>     important to mention that most of servers supports it otherwise it is
>     hardly usable (using lib would be a nightmare).
>
>
>     Romain Manni-Bucau
>     Twitter: @rmannibucau
>     Blog: http://rmannibucau.wordpress.com/
>     LinkedIn: http://fr.linkedin.com/in/rmannibucau
>     Github: https://github.com/rmannibucau
>
>
>     2014-08-22 11:10 GMT+02:00 Jozef Hartinger <jharting at redhat.com
>     <mailto:jharting at redhat.com>>:
>     > Hi John,
>     >
>     > no, the interceptor will only be enabled in war's
>     WEB-INF/classes. Other
>     > JARs need to enable the interceptor in their beans.xml file to
>     use it.
>     >
>     > Jozef
>     >
>     >
>     > On 08/21/2014 08:43 PM, John D. Ament wrote:
>     >
>     > Hi,
>     >
>     > Let's suppose I'm deploying a WAR file w/ multiple JAR files. 
>     The WAR has a
>     > beans.xml w/ interceptors defined in it.  The JARs each have
>     beans.xml, but
>     > no interceptors defined within them.
>     >
>     > Should the interceptors in the WAR apply to all of the JAR files?
>     >
>     > Thanks,
>     >
>     > John
>     >
>     >
>     >
>     > _______________________________________________
>     > cdi-dev mailing list
>     > cdi-dev at lists.jboss.org <mailto:cdi-dev at lists.jboss.org>
>     > https://lists.jboss.org/mailman/listinfo/cdi-dev
>     >
>     >
>     >
>     > _______________________________________________
>     > cdi-dev mailing list
>     > cdi-dev at lists.jboss.org <mailto:cdi-dev at lists.jboss.org>
>     > https://lists.jboss.org/mailman/listinfo/cdi-dev
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20140823/02839558/attachment.html 

From issues at jboss.org  Mon Aug 25 04:44:00 2014
From: issues at jboss.org (Martin Kouba (JIRA))
Date: Mon, 25 Aug 2014 04:44:00 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-414) Support for "self" injection
In-Reply-To: <JIRA.12528622.1388866578000@Atlassian.JIRA>
References: <JIRA.12528622.1388866578000@Atlassian.JIRA>
	<JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528622.1388866578000.4344.1408956240949@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/CDI-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995317#comment-12995317 ] 

Martin Kouba commented on CDI-414:
----------------------------------

{quote}
Of course @Inject in @Stateless beans should work the same way as @EJB. It actually should really make no difference if you resolve the EJB via @Inject, @EJB or manually from JNDI. If this doesn't work it is a bug imo. 
{quote}
Well, this is not required by the spec. A SLSB must belong to the @Dependent pseudo-scope and the container is not required to support circular dependencies where every bean in the chain has a pseudo-scope. So there is a difference. In my opinion, SLSBs should belong to a special scope (see also CDI-278).

> Support for "self" injection
> ----------------------------
>
>                 Key: CDI-414
>                 URL: https://issues.jboss.org/browse/CDI-414
>             Project: CDI Specification Issues
>          Issue Type: Bug
>          Components: Resolution
>            Reporter: arjan tijms
>
> Many features of CDI and EJB work by means of a proxy that intercepts calls and adds 'aspects'. In Java it's however not possible to decorate the {{this}} pointer, so methods called on the same bean instance from within a method in the bean do not get their 'aspects' applied.
> This is a well known limitation, but in EJB it's possible to work around this by injecting a bean into itself. E.g.
> {code}
> @Stateless
> public class Foo {
>     @EJB
>     private Foo self;
>     // ...
> }
> {code}
> Also see http://adam-bien.com/roller/abien/entry/how_to_self_invoke_ejb
> Unfortunately using CDI and {{@Inject}} this doesn't work. Weld for instance fails the deployment and logs:
> {noformat}
> WELD-001443 Pseudo scoped bean has circular dependencies.
> {noformat}
> See also: http://adam-bien.com/roller/abien/entry/inject_vs_ejb
> Although there are workarounds, it would be great if {{@Inject}} in combination with CDI could support self injection as well.
> With that projects migrating from {{@EJB}} to {{@Inject}} can do so more easily and the capability can be convenient for new projects as well (e.g. calling two separate {{@Transactional}} methods from a single method without being required to create a new bean).



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Mon Aug 25 09:04:01 2014
From: issues at jboss.org (Mark Struberg (JIRA))
Date: Mon, 25 Aug 2014 09:04:01 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-414) Support for "self" injection
In-Reply-To: <JIRA.12528622.1388866578000@Atlassian.JIRA>
References: <JIRA.12528622.1388866578000@Atlassian.JIRA>
	<JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528622.1388866578000.5155.1408971841136@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/CDI-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995420#comment-12995420 ] 

Mark Struberg commented on CDI-414:
-----------------------------------

Martin, the CDI EG has discussed this in length. If you check our discussion in CDI-243 and CDI-278 you will remember that the reason for this wording was exactly _because_ the EJB must already provide their own proxies and the CDI Container does _not_ add _another_ proxy to it. But of course the original EJB proxy *must be there* as required by the spec. 


> Support for "self" injection
> ----------------------------
>
>                 Key: CDI-414
>                 URL: https://issues.jboss.org/browse/CDI-414
>             Project: CDI Specification Issues
>          Issue Type: Bug
>          Components: Resolution
>            Reporter: arjan tijms
>
> Many features of CDI and EJB work by means of a proxy that intercepts calls and adds 'aspects'. In Java it's however not possible to decorate the {{this}} pointer, so methods called on the same bean instance from within a method in the bean do not get their 'aspects' applied.
> This is a well known limitation, but in EJB it's possible to work around this by injecting a bean into itself. E.g.
> {code}
> @Stateless
> public class Foo {
>     @EJB
>     private Foo self;
>     // ...
> }
> {code}
> Also see http://adam-bien.com/roller/abien/entry/how_to_self_invoke_ejb
> Unfortunately using CDI and {{@Inject}} this doesn't work. Weld for instance fails the deployment and logs:
> {noformat}
> WELD-001443 Pseudo scoped bean has circular dependencies.
> {noformat}
> See also: http://adam-bien.com/roller/abien/entry/inject_vs_ejb
> Although there are workarounds, it would be great if {{@Inject}} in combination with CDI could support self injection as well.
> With that projects migrating from {{@EJB}} to {{@Inject}} can do so more easily and the capability can be convenient for new projects as well (e.g. calling two separate {{@Transactional}} methods from a single method without being required to create a new bean).



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Mon Aug 25 09:29:00 2014
From: issues at jboss.org (Martin Kouba (JIRA))
Date: Mon, 25 Aug 2014 09:29:00 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-414) Support for "self" injection
In-Reply-To: <JIRA.12528622.1388866578000@Atlassian.JIRA>
References: <JIRA.12528622.1388866578000@Atlassian.JIRA>
	<JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528622.1388866578000.5357.1408973340941@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/CDI-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995444#comment-12995444 ] 

Martin Kouba commented on CDI-414:
----------------------------------

Mark, I don't question the existence of EJB proxies. My point is that the CDI spec does not force the implementation to support the self-injection example as given in the description of this issue (because of SLSBs are @Dependent).

> Support for "self" injection
> ----------------------------
>
>                 Key: CDI-414
>                 URL: https://issues.jboss.org/browse/CDI-414
>             Project: CDI Specification Issues
>          Issue Type: Bug
>          Components: Resolution
>            Reporter: arjan tijms
>
> Many features of CDI and EJB work by means of a proxy that intercepts calls and adds 'aspects'. In Java it's however not possible to decorate the {{this}} pointer, so methods called on the same bean instance from within a method in the bean do not get their 'aspects' applied.
> This is a well known limitation, but in EJB it's possible to work around this by injecting a bean into itself. E.g.
> {code}
> @Stateless
> public class Foo {
>     @EJB
>     private Foo self;
>     // ...
> }
> {code}
> Also see http://adam-bien.com/roller/abien/entry/how_to_self_invoke_ejb
> Unfortunately using CDI and {{@Inject}} this doesn't work. Weld for instance fails the deployment and logs:
> {noformat}
> WELD-001443 Pseudo scoped bean has circular dependencies.
> {noformat}
> See also: http://adam-bien.com/roller/abien/entry/inject_vs_ejb
> Although there are workarounds, it would be great if {{@Inject}} in combination with CDI could support self injection as well.
> With that projects migrating from {{@EJB}} to {{@Inject}} can do so more easily and the capability can be convenient for new projects as well (e.g. calling two separate {{@Transactional}} methods from a single method without being required to create a new bean).



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Mon Aug 25 13:06:01 2014
From: issues at jboss.org (Jason Porter (JIRA))
Date: Mon, 25 Aug 2014 13:06:01 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-4) Need a way to provide ordering for
 Event observers
In-Reply-To: <JIRA.12415300.1280185626000@Atlassian.JIRA>
References: <JIRA.12415300.1280185626000@Atlassian.JIRA>
	<JIRA.12415300.1280185626000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12415300.1280185626000.6129.1408986361625@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/CDI-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995531#comment-12995531 ] 

Jason Porter commented on CDI-4:
--------------------------------

If we have something at the same priority level, is it just unspecified behavior?

> Need a way to provide ordering for Event observers
> --------------------------------------------------
>
>                 Key: CDI-4
>                 URL: https://issues.jboss.org/browse/CDI-4
>             Project: CDI Specification Issues
>          Issue Type: Feature Request
>          Components: Events, Portable Extensions
>    Affects Versions: 1.0
>         Environment: All
>            Reporter: Lincoln Baxter III
>            Assignee: Pete Muir
>             Fix For: 2.0 (discussion)
>
>
> There needs to be a way to specify some kind of ordering for Event observers. 
> Understandably, this is somewhat counter-intuitive to the general concept of observing an event, but there is going to be need for this in an upcoming JBoss project. While it can be done manually, it might be nice to have a built-in API.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Mon Aug 25 13:55:01 2014
From: issues at jboss.org (Mark Struberg (JIRA))
Date: Mon, 25 Aug 2014 13:55:01 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-4) Need a way to provide ordering for
 Event observers
In-Reply-To: <JIRA.12415300.1280185626000@Atlassian.JIRA>
References: <JIRA.12415300.1280185626000@Atlassian.JIRA>
	<JIRA.12415300.1280185626000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12415300.1280185626000.6326.1408989301684@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/CDI-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995551#comment-12995551 ] 

Mark Struberg commented on CDI-4:
---------------------------------

[~lightguard]] same unspecified behaviour as we have today for ALL observers ;)

> Need a way to provide ordering for Event observers
> --------------------------------------------------
>
>                 Key: CDI-4
>                 URL: https://issues.jboss.org/browse/CDI-4
>             Project: CDI Specification Issues
>          Issue Type: Feature Request
>          Components: Events, Portable Extensions
>    Affects Versions: 1.0
>         Environment: All
>            Reporter: Lincoln Baxter III
>            Assignee: Pete Muir
>             Fix For: 2.0 (discussion)
>
>
> There needs to be a way to specify some kind of ordering for Event observers. 
> Understandably, this is somewhat counter-intuitive to the general concept of observing an event, but there is going to be need for this in an upcoming JBoss project. While it can be done manually, it might be nice to have a built-in API.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Tue Aug 26 04:48:01 2014
From: issues at jboss.org (Mark Struberg (JIRA))
Date: Tue, 26 Aug 2014 04:48:01 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-414) Support for "self" injection
In-Reply-To: <JIRA.12528622.1388866578000@Atlassian.JIRA>
References: <JIRA.12528622.1388866578000@Atlassian.JIRA>
	<JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528622.1388866578000.7406.1409042881158@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/CDI-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995663#comment-12995663 ] 

Mark Struberg commented on CDI-414:
-----------------------------------

The usage of '@Dependent' on our side was just a way to say 'EJB should take care about all the proxies and interceptors'.

In the end, it must not make any difference whether you use @Inject or @EJB to inject the SLSB into itself. If it does, then this is a container bug.

> Support for "self" injection
> ----------------------------
>
>                 Key: CDI-414
>                 URL: https://issues.jboss.org/browse/CDI-414
>             Project: CDI Specification Issues
>          Issue Type: Bug
>          Components: Resolution
>            Reporter: arjan tijms
>
> Many features of CDI and EJB work by means of a proxy that intercepts calls and adds 'aspects'. In Java it's however not possible to decorate the {{this}} pointer, so methods called on the same bean instance from within a method in the bean do not get their 'aspects' applied.
> This is a well known limitation, but in EJB it's possible to work around this by injecting a bean into itself. E.g.
> {code}
> @Stateless
> public class Foo {
>     @EJB
>     private Foo self;
>     // ...
> }
> {code}
> Also see http://adam-bien.com/roller/abien/entry/how_to_self_invoke_ejb
> Unfortunately using CDI and {{@Inject}} this doesn't work. Weld for instance fails the deployment and logs:
> {noformat}
> WELD-001443 Pseudo scoped bean has circular dependencies.
> {noformat}
> See also: http://adam-bien.com/roller/abien/entry/inject_vs_ejb
> Although there are workarounds, it would be great if {{@Inject}} in combination with CDI could support self injection as well.
> With that projects migrating from {{@EJB}} to {{@Inject}} can do so more easily and the capability can be convenient for new projects as well (e.g. calling two separate {{@Transactional}} methods from a single method without being required to create a new bean).



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Tue Aug 26 04:52:59 2014
From: issues at jboss.org (Martin Kouba (JIRA))
Date: Tue, 26 Aug 2014 04:52:59 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-414) Support for "self" injection
In-Reply-To: <JIRA.12528622.1388866578000@Atlassian.JIRA>
References: <JIRA.12528622.1388866578000@Atlassian.JIRA>
	<JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528622.1388866578000.7434.1409043179835@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/CDI-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995669#comment-12995669 ] 

Martin Kouba commented on CDI-414:
----------------------------------

{quote}
In the end, it must not make any difference whether you use @Inject or @EJB to inject the SLSB into itself.
{quote}
Then we must standardize this somehow...

> Support for "self" injection
> ----------------------------
>
>                 Key: CDI-414
>                 URL: https://issues.jboss.org/browse/CDI-414
>             Project: CDI Specification Issues
>          Issue Type: Bug
>          Components: Resolution
>            Reporter: arjan tijms
>
> Many features of CDI and EJB work by means of a proxy that intercepts calls and adds 'aspects'. In Java it's however not possible to decorate the {{this}} pointer, so methods called on the same bean instance from within a method in the bean do not get their 'aspects' applied.
> This is a well known limitation, but in EJB it's possible to work around this by injecting a bean into itself. E.g.
> {code}
> @Stateless
> public class Foo {
>     @EJB
>     private Foo self;
>     // ...
> }
> {code}
> Also see http://adam-bien.com/roller/abien/entry/how_to_self_invoke_ejb
> Unfortunately using CDI and {{@Inject}} this doesn't work. Weld for instance fails the deployment and logs:
> {noformat}
> WELD-001443 Pseudo scoped bean has circular dependencies.
> {noformat}
> See also: http://adam-bien.com/roller/abien/entry/inject_vs_ejb
> Although there are workarounds, it would be great if {{@Inject}} in combination with CDI could support self injection as well.
> With that projects migrating from {{@EJB}} to {{@Inject}} can do so more easily and the capability can be convenient for new projects as well (e.g. calling two separate {{@Transactional}} methods from a single method without being required to create a new bean).



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Tue Aug 26 05:07:03 2014
From: issues at jboss.org (Mark Struberg (JIRA))
Date: Tue, 26 Aug 2014 05:07:03 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-414) Support for "self" injection
In-Reply-To: <JIRA.12528622.1388866578000@Atlassian.JIRA>
References: <JIRA.12528622.1388866578000@Atlassian.JIRA>
	<JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528622.1388866578000.7499.1409044023140@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/CDI-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995674#comment-12995674 ] 

Mark Struberg commented on CDI-414:
-----------------------------------

Had an offline conversation with Martin. The real reason is not the interceptor but the check in Weld that you cannot inject itself in @Dependent scoped beans. Of course a SLSB is not _really_ @Dependent but this was only a hack to describe that CDI should not apply own proxies. But this triggers the aforementioned check in Weld. Which is not wrong from a plain spec perspective - but it is not really helpful.

In OWB we do not check for cyclic injection at all as there are just too many scenarios where it can happen.E.g A->B->A, A->B->C->A,... + all combinations with @PostConstruct, @Inject methods, @Inject constructors, etc. You will get a stackoverflow anyway if you do this. Not as nice a msg as in Weld, but we don't restrict constellations which are perfectly valid that way ;)

Please also note that the same might happen if you use @Scope scopes in Weld. Even if those non-299 scopes bring their own proxies, correct Martin?

> Support for "self" injection
> ----------------------------
>
>                 Key: CDI-414
>                 URL: https://issues.jboss.org/browse/CDI-414
>             Project: CDI Specification Issues
>          Issue Type: Bug
>          Components: Resolution
>            Reporter: arjan tijms
>
> Many features of CDI and EJB work by means of a proxy that intercepts calls and adds 'aspects'. In Java it's however not possible to decorate the {{this}} pointer, so methods called on the same bean instance from within a method in the bean do not get their 'aspects' applied.
> This is a well known limitation, but in EJB it's possible to work around this by injecting a bean into itself. E.g.
> {code}
> @Stateless
> public class Foo {
>     @EJB
>     private Foo self;
>     // ...
> }
> {code}
> Also see http://adam-bien.com/roller/abien/entry/how_to_self_invoke_ejb
> Unfortunately using CDI and {{@Inject}} this doesn't work. Weld for instance fails the deployment and logs:
> {noformat}
> WELD-001443 Pseudo scoped bean has circular dependencies.
> {noformat}
> See also: http://adam-bien.com/roller/abien/entry/inject_vs_ejb
> Although there are workarounds, it would be great if {{@Inject}} in combination with CDI could support self injection as well.
> With that projects migrating from {{@EJB}} to {{@Inject}} can do so more easily and the capability can be convenient for new projects as well (e.g. calling two separate {{@Transactional}} methods from a single method without being required to create a new bean).



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Tue Aug 26 05:25:01 2014
From: issues at jboss.org (Martin Kouba (JIRA))
Date: Tue, 26 Aug 2014 05:25:01 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-414) Support for "self" injection
In-Reply-To: <JIRA.12528622.1388866578000@Atlassian.JIRA>
References: <JIRA.12528622.1388866578000@Atlassian.JIRA>
	<JIRA.12528622.1388866578000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12528622.1388866578000.7584.1409045101104@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/CDI-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995687#comment-12995687 ] 

Martin Kouba commented on CDI-414:
----------------------------------

Yes, there must be at least one normal-scoped bean participating in the chain of dependencies. Otherwise the deployment fails.

> Support for "self" injection
> ----------------------------
>
>                 Key: CDI-414
>                 URL: https://issues.jboss.org/browse/CDI-414
>             Project: CDI Specification Issues
>          Issue Type: Bug
>          Components: Resolution
>            Reporter: arjan tijms
>
> Many features of CDI and EJB work by means of a proxy that intercepts calls and adds 'aspects'. In Java it's however not possible to decorate the {{this}} pointer, so methods called on the same bean instance from within a method in the bean do not get their 'aspects' applied.
> This is a well known limitation, but in EJB it's possible to work around this by injecting a bean into itself. E.g.
> {code}
> @Stateless
> public class Foo {
>     @EJB
>     private Foo self;
>     // ...
> }
> {code}
> Also see http://adam-bien.com/roller/abien/entry/how_to_self_invoke_ejb
> Unfortunately using CDI and {{@Inject}} this doesn't work. Weld for instance fails the deployment and logs:
> {noformat}
> WELD-001443 Pseudo scoped bean has circular dependencies.
> {noformat}
> See also: http://adam-bien.com/roller/abien/entry/inject_vs_ejb
> Although there are workarounds, it would be great if {{@Inject}} in combination with CDI could support self injection as well.
> With that projects migrating from {{@EJB}} to {{@Inject}} can do so more easily and the capability can be convenient for new projects as well (e.g. calling two separate {{@Transactional}} methods from a single method without being required to create a new bean).



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Tue Aug 26 15:58:59 2014
From: issues at jboss.org (Alexandre Porcelli (JIRA))
Date: Tue, 26 Aug 2014 15:58:59 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-454) Provide Event scope (in order to
 enable broadcast on Container level)
In-Reply-To: <JIRA.12550298.1409083093000@Atlassian.JIRA>
References: <JIRA.12550298.1409083093000@Atlassian.JIRA>
	<JIRA.12550298.1409083093913@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12550298.1409083093000.9728.1409083139535@Atlassian.JIRA>

Alexandre Porcelli created CDI-454:
--------------------------------------

             Summary: Provide Event scope (in order to enable broadcast on Container level)
                 Key: CDI-454
                 URL: https://issues.jboss.org/browse/CDI-454
             Project: CDI Specification Issues
          Issue Type: Feature Request
    Affects Versions: 2.0 (discussion)
            Reporter: Alexandre Porcelli


Events could be scoped, some possible scopes are: Library (jar), Application (war/ear) or Container (server).

The most relevant scope would be the Container, as it would bring a great integration mechanism between deployed applications.




--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Tue Aug 26 16:21:00 2014
From: issues at jboss.org (Antonio Goncalves (JIRA))
Date: Tue, 26 Aug 2014 16:21:00 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-454) Provide Event scope (in order to
 enable broadcast on Container level)
In-Reply-To: <JIRA.12550298.1409083093000@Atlassian.JIRA>
References: <JIRA.12550298.1409083093000@Atlassian.JIRA>
	<JIRA.12550298.1409083093000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12550298.1409083093000.9744.1409084460055@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/CDI-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995950#comment-12995950 ] 

Antonio Goncalves commented on CDI-454:
---------------------------------------

Following the {{Priority}} annotation terms, we could have platform, library and application.

As a reminder : 
{code}
	public static final int PLATFORM_BEFORE = 0;
	public static final int LIBRARY_BEFORE = 1000;
	public static final int APPLICATION = 2000;
        ...
{code}

> Provide Event scope (in order to enable broadcast on Container level)
> ---------------------------------------------------------------------
>
>                 Key: CDI-454
>                 URL: https://issues.jboss.org/browse/CDI-454
>             Project: CDI Specification Issues
>          Issue Type: Feature Request
>    Affects Versions: 2.0 (discussion)
>            Reporter: Alexandre Porcelli
>
> Events could be scoped, some possible scopes are: Library (jar), Application (war/ear) or Container (server).
> The most relevant scope would be the Container, as it would bring a great integration mechanism between deployed applications.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Tue Aug 26 16:21:59 2014
From: issues at jboss.org (Antonio Goncalves (JIRA))
Date: Tue, 26 Aug 2014 16:21:59 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-454) Provide Event scope (in order to
 enable broadcast on Container level)
In-Reply-To: <JIRA.12550298.1409083093000@Atlassian.JIRA>
References: <JIRA.12550298.1409083093000@Atlassian.JIRA>
	<JIRA.12550298.1409083093000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12550298.1409083093000.9752.1409084519754@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/CDI-454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12995950#comment-12995950 ] 

Antonio Goncalves edited comment on CDI-454 at 8/26/14 4:21 PM:
----------------------------------------------------------------

Following the {{Priority}} annotation, we could have the following terms : Platform, Library and Application.

As a reminder : 
{code}
	public static final int PLATFORM_BEFORE = 0;
	public static final int LIBRARY_BEFORE = 1000;
	public static final int APPLICATION = 2000;
        ...
{code}


was (Author: agoncal):
Following the {{Priority}} annotation terms, we could have platform, library and application.

As a reminder : 
{code}
	public static final int PLATFORM_BEFORE = 0;
	public static final int LIBRARY_BEFORE = 1000;
	public static final int APPLICATION = 2000;
        ...
{code}

> Provide Event scope (in order to enable broadcast on Container level)
> ---------------------------------------------------------------------
>
>                 Key: CDI-454
>                 URL: https://issues.jboss.org/browse/CDI-454
>             Project: CDI Specification Issues
>          Issue Type: Feature Request
>    Affects Versions: 2.0 (discussion)
>            Reporter: Alexandre Porcelli
>
> Events could be scoped, some possible scopes are: Library (jar), Application (war/ear) or Container (server).
> The most relevant scope would be the Container, as it would bring a great integration mechanism between deployed applications.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From omeuefilipe at gmail.com  Tue Aug 26 17:02:15 2014
From: omeuefilipe at gmail.com (Filipe Portes)
Date: Tue, 26 Aug 2014 18:02:15 -0300
Subject: [cdi-dev] Introduce myself
Message-ID: <CAKwwkgSK0T8n+nf+3t6PyHk4omkdvTgS7n2d3zZEg=+FwN3zuA@mail.gmail.com>

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20140826/dc816956/attachment.html 

From antoine at sabot-durand.net  Wed Aug 27 03:30:37 2014
From: antoine at sabot-durand.net (Antoine Sabot-Durand)
Date: Wed, 27 Aug 2014 09:30:37 +0200
Subject: [cdi-dev] Introduce myself
In-Reply-To: <CAKwwkgSK0T8n+nf+3t6PyHk4omkdvTgS7n2d3zZEg=+FwN3zuA@mail.gmail.com>
References: <CAKwwkgSK0T8n+nf+3t6PyHk4omkdvTgS7n2d3zZEg=+FwN3zuA@mail.gmail.com>
Message-ID: <E2CD5830-179A-47D0-A636-6AA87FF159EA@sabot-durand.net>

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/ <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 at 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 at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20140827/5cf7f23c/attachment.html 

From antonio.goncalves at gmail.com  Wed Aug 27 03:34:51 2014
From: antonio.goncalves at gmail.com (Antonio Goncalves)
Date: Wed, 27 Aug 2014 09:34:51 +0200
Subject: [cdi-dev] Introduce myself
In-Reply-To: <E2CD5830-179A-47D0-A636-6AA87FF159EA@sabot-durand.net>
References: <CAKwwkgSK0T8n+nf+3t6PyHk4omkdvTgS7n2d3zZEg=+FwN3zuA@mail.gmail.com>
	<E2CD5830-179A-47D0-A636-6AA87FF159EA@sabot-durand.net>
Message-ID: <CA+ZZq9_V5oSZ0QLpaDwhfvXjzrF6Gapjmf=yQX27=FJ+GdHN7Q@mail.gmail.com>

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 at 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 at 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 at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev
>
>
>
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at 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/fadb3a54/attachment.html 

From radhakrishnan.mohan at gmail.com  Wed Aug 27 04:20:43 2014
From: radhakrishnan.mohan at gmail.com (Mohan Radhakrishnan)
Date: Wed, 27 Aug 2014 13:50:43 +0530
Subject: [cdi-dev] Introduce myself
In-Reply-To: <CA+ZZq9_V5oSZ0QLpaDwhfvXjzrF6Gapjmf=yQX27=FJ+GdHN7Q@mail.gmail.com>
References: <CAKwwkgSK0T8n+nf+3t6PyHk4omkdvTgS7n2d3zZEg=+FwN3zuA@mail.gmail.com>
	<E2CD5830-179A-47D0-A636-6AA87FF159EA@sabot-durand.net>
	<CA+ZZq9_V5oSZ0QLpaDwhfvXjzrF6Gapjmf=yQX27=FJ+GdHN7Q@mail.gmail.com>
Message-ID: <CAOoXFP_gte5UUW_uXs48fiEj9nuqs8U0KmN-sh4mgT=fUTLfvw@mail.gmail.com>

Hi,
          AOP is mentioned in
http://www.cdi-spec.org/news/2014/08/26/CDI-20_needs_you/. I have used
AspectJ. Do I qualify (outside EG )if I also know Java upto JDK 8 ? No
paperwork ?

Thanks,
Mohan


On Wed, Aug 27, 2014 at 1:04 PM, Antonio Goncalves <
antonio.goncalves at gmail.com> wrote:

> 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 at 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 at 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 at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/cdi-dev
>>
>>
>>
>> _______________________________________________
>> cdi-dev mailing list
>> cdi-dev at 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 at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20140827/aea9cfb4/attachment.html 

From pmuir at redhat.com  Wed Aug 27 05:54:48 2014
From: pmuir at redhat.com (Pete Muir)
Date: Wed, 27 Aug 2014 10:54:48 +0100
Subject: [cdi-dev] Introduce myself
In-Reply-To: <CAOoXFP_gte5UUW_uXs48fiEj9nuqs8U0KmN-sh4mgT=fUTLfvw@mail.gmail.com>
References: <CAKwwkgSK0T8n+nf+3t6PyHk4omkdvTgS7n2d3zZEg=+FwN3zuA@mail.gmail.com>
	<E2CD5830-179A-47D0-A636-6AA87FF159EA@sabot-durand.net>
	<CA+ZZq9_V5oSZ0QLpaDwhfvXjzrF6Gapjmf=yQX27=FJ+GdHN7Q@mail.gmail.com>
	<CAOoXFP_gte5UUW_uXs48fiEj9nuqs8U0KmN-sh4mgT=fUTLfvw@mail.gmail.com>
Message-ID: <0DDE71D8-6519-4655-AEC4-09AEAEE255A0@redhat.com>

Definitely!

On 27 Aug 2014, at 09:20, Mohan Radhakrishnan <radhakrishnan.mohan at gmail.com> wrote:

> Hi,
>           AOP is mentioned in http://www.cdi-spec.org/news/2014/08/26/CDI-20_needs_you/. I have used AspectJ. Do I qualify (outside EG )if I also know Java upto JDK 8 ? No paperwork ?
> 
> Thanks,
> Mohan
> 
> 
> On Wed, Aug 27, 2014 at 1:04 PM, Antonio Goncalves <antonio.goncalves at gmail.com> wrote:
> 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 at 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 at 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 - @gojava
>> _______________________________________________
>> cdi-dev mailing list
>> cdi-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/cdi-dev
> 
> 
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev
> 
> 
> 
> -- 
> Antonio Goncalves 
> Software architect, Java Champion and Pluralsight author
> 
> Web site | Twitter | LinkedIn | Pluralsight | Paris JUG | Devoxx France
> 
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev
> 
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev



From antoine at sabot-durand.net  Wed Aug 27 06:35:20 2014
From: antoine at sabot-durand.net (Antoine Sabot-Durand)
Date: Wed, 27 Aug 2014 12:35:20 +0200
Subject: [cdi-dev] Introduce myself
In-Reply-To: <CAOoXFP_gte5UUW_uXs48fiEj9nuqs8U0KmN-sh4mgT=fUTLfvw@mail.gmail.com>
References: <CAKwwkgSK0T8n+nf+3t6PyHk4omkdvTgS7n2d3zZEg=+FwN3zuA@mail.gmail.com>
	<E2CD5830-179A-47D0-A636-6AA87FF159EA@sabot-durand.net>
	<CA+ZZq9_V5oSZ0QLpaDwhfvXjzrF6Gapjmf=yQX27=FJ+GdHN7Q@mail.gmail.com>
	<CAOoXFP_gte5UUW_uXs48fiEj9nuqs8U0KmN-sh4mgT=fUTLfvw@mail.gmail.com>
Message-ID: <A7CBD427-E3D7-4EF4-94E6-6FDD030392EE@sabot-durand.net>

Hi Mohan,


To be perfectly clear, every one is welcome on the EG and more broadly on the project. There are no exam and we won?t ask for your degrees ;). My mention in the post was only to warn super beginner in Java that they could feel lost and that we won?t have time to teach them the basic.

Now regarding the official EG application, you can do as you want. Start your contribution outside and if you feel like it, apply later (or not) it?s up to you.

Welcome

Antoine


> Le 27 ao?t 2014 ? 10:20, Mohan Radhakrishnan <radhakrishnan.mohan at gmail.com> a ?crit :
> 
> Hi,
>           AOP is mentioned in http://www.cdi-spec.org/news/2014/08/26/CDI-20_needs_you/ <http://www.cdi-spec.org/news/2014/08/26/CDI-20_needs_you/>. I have used AspectJ. Do I qualify (outside EG )if I also know Java upto JDK 8 ? No paperwork ?
> 
> Thanks,
> Mohan
> 
> 
> On Wed, Aug 27, 2014 at 1:04 PM, Antonio Goncalves <antonio.goncalves at gmail.com <mailto:antonio.goncalves at gmail.com>> wrote:
> 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 at sabot-durand.net <mailto:antoine at 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/ <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 at gmail.com <mailto:omeuefilipe at 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 at lists.jboss.org <mailto:cdi-dev at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/cdi-dev <https://lists.jboss.org/mailman/listinfo/cdi-dev>
> 
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at lists.jboss.org <mailto:cdi-dev at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/cdi-dev <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 at lists.jboss.org <mailto:cdi-dev at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/cdi-dev <https://lists.jboss.org/mailman/listinfo/cdi-dev>
> 
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20140827/0e1e9a8b/attachment.html 

From antoine at sabot-durand.net  Wed Aug 27 06:37:10 2014
From: antoine at sabot-durand.net (Antoine Sabot-Durand)
Date: Wed, 27 Aug 2014 12:37:10 +0200
Subject: [cdi-dev] Introduce myself
In-Reply-To: <CA+ZZq9_V5oSZ0QLpaDwhfvXjzrF6Gapjmf=yQX27=FJ+GdHN7Q@mail.gmail.com>
References: <CAKwwkgSK0T8n+nf+3t6PyHk4omkdvTgS7n2d3zZEg=+FwN3zuA@mail.gmail.com>
	<E2CD5830-179A-47D0-A636-6AA87FF159EA@sabot-durand.net>
	<CA+ZZq9_V5oSZ0QLpaDwhfvXjzrF6Gapjmf=yQX27=FJ+GdHN7Q@mail.gmail.com>
Message-ID: <0546363E-823A-4B7B-95F0-27D872D171A3@sabot-durand.net>

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 at 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 at sabot-durand.net <mailto:antoine at 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/ <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 at gmail.com <mailto:omeuefilipe at 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 at lists.jboss.org <mailto:cdi-dev at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/cdi-dev <https://lists.jboss.org/mailman/listinfo/cdi-dev>
> 
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at lists.jboss.org <mailto:cdi-dev at lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/cdi-dev <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/5f53053b/attachment.html 

From antoine at sabot-durand.net  Wed Aug 27 06:46:03 2014
From: antoine at sabot-durand.net (Antoine Sabot-Durand)
Date: Wed, 27 Aug 2014 12:46:03 +0200
Subject: [cdi-dev] More info on EG application
Message-ID: <C7C48CBC-753D-41AC-BEFE-2623437AE5A9@sabot-durand.net>

Hi all,


Just to let you know that you can apply to the Expert Group on the JCP site (Remember that it?s not mandatory to be part o the project).

To do so, you?ll have to be a JCP member. If you are not a jcp member yet check the info here : https://jcp.org/en/participation/membership <https://jcp.org/en/participation/membership>
When ready you can apply to JSR 365 EG from the specification page : https://jcp.org/en/jsr/detail?id=365 <https://jcp.org/en/jsr/detail?id=365>

We already have accepted 5 EG applications. The JCP organisation (PMO) has still to validate them, that?s why they are not visible in the EG yet.

Antoine
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20140827/4968b47b/attachment.html 

From john.d.ament at gmail.com  Wed Aug 27 07:03:08 2014
From: john.d.ament at gmail.com (John D. Ament)
Date: Wed, 27 Aug 2014 07:03:08 -0400
Subject: [cdi-dev] Introduce myself
In-Reply-To: <0546363E-823A-4B7B-95F0-27D872D171A3@sabot-durand.net>
References: <CAKwwkgSK0T8n+nf+3t6PyHk4omkdvTgS7n2d3zZEg=+FwN3zuA@mail.gmail.com>
	<E2CD5830-179A-47D0-A636-6AA87FF159EA@sabot-durand.net>
	<CA+ZZq9_V5oSZ0QLpaDwhfvXjzrF6Gapjmf=yQX27=FJ+GdHN7Q@mail.gmail.com>
	<0546363E-823A-4B7B-95F0-27D872D171A3@sabot-durand.net>
Message-ID: <CAOqetn858KEPudxHqSCgLkYj7W6SdmZUSQBpn8YD+_7fDH3hDw@mail.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 at 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 at 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 at 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 at 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 at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/cdi-dev
>>
>>
>>
>> _______________________________________________
>> cdi-dev mailing list
>> cdi-dev at 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 at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20140827/57795157/attachment-0001.html 

From werner.keil at gmail.com  Wed Aug 27 07:13:42 2014
From: werner.keil at gmail.com (Werner Keil)
Date: Wed, 27 Aug 2014 13:13:42 +0200
Subject: [cdi-dev] cdi-dev Digest, Vol 45, Issue 10
In-Reply-To: <mailman.19772.1409137394.2342.cdi-dev@lists.jboss.org>
References: <mailman.19772.1409137394.2342.cdi-dev@lists.jboss.org>
Message-ID: <CAAGawe356u+HciMsEJb=qWohF5O+uhoV9P6yijYxHBSnaQhetg@mail.gmail.com>

Thanks for the reminder, I mentioned when confirming to support CDI 2, that
based on working in the old EG or related efforts like Agorava, I'd love to
join this EG.

When I'm online later I'll fill out that form, too. And the "usual" Exhibit
B[?]

Werner


On Wed, Aug 27, 2014 at 1:03 PM, <cdi-dev-request at lists.jboss.org> wrote:

> Send cdi-dev mailing list submissions to
>         cdi-dev at 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 at lists.jboss.org
>
> You can reach the person managing the list at
>         cdi-dev-owner at 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 (Antoine Sabot-Durand)
>    2. Re: Introduce myself (Antoine Sabot-Durand)
>    3. More info on EG application (Antoine Sabot-Durand)
>    4. Re: Introduce myself (John D. Ament)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 27 Aug 2014 12:35:20 +0200
> From: Antoine Sabot-Durand <antoine at sabot-durand.net>
> Subject: Re: [cdi-dev] Introduce myself
> To: Mohan Radhakrishnan <radhakrishnan.mohan at gmail.com>
> Cc: cdi-dev at lists.jboss.org
> Message-ID: <A7CBD427-E3D7-4EF4-94E6-6FDD030392EE at sabot-durand.net>
> Content-Type: text/plain; charset="utf-8"
>
> Hi Mohan,
>
>
> To be perfectly clear, every one is welcome on the EG and more broadly on
> the project. There are no exam and we won?t ask for your degrees ;). My
> mention in the post was only to warn super beginner in Java that they could
> feel lost and that we won?t have time to teach them the basic.
>
> Now regarding the official EG application, you can do as you want. Start
> your contribution outside and if you feel like it, apply later (or not)
> it?s up to you.
>
> Welcome
>
> Antoine
>
>
> > Le 27 ao?t 2014 ? 10:20, Mohan Radhakrishnan <
> radhakrishnan.mohan at gmail.com> a ?crit :
> >
> > Hi,
> >           AOP is mentioned in
> http://www.cdi-spec.org/news/2014/08/26/CDI-20_needs_you/ <
> http://www.cdi-spec.org/news/2014/08/26/CDI-20_needs_you/>. I have used
> AspectJ. Do I qualify (outside EG )if I also know Java upto JDK 8 ? No
> paperwork ?
> >
> > Thanks,
> > Mohan
> >
> >
> > On Wed, Aug 27, 2014 at 1:04 PM, Antonio Goncalves <
> antonio.goncalves at gmail.com <mailto:antonio.goncalves at gmail.com>> wrote:
> > 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 at sabot-durand.net <mailto:antoine at 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/ <
> 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 at gmail.com <mailto:
> omeuefilipe at 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 at lists.jboss.org <mailto:cdi-dev at lists.jboss.org>
> >> https://lists.jboss.org/mailman/listinfo/cdi-dev <
> https://lists.jboss.org/mailman/listinfo/cdi-dev>
> >
> > _______________________________________________
> > cdi-dev mailing list
> > cdi-dev at lists.jboss.org <mailto:cdi-dev at lists.jboss.org>
> > https://lists.jboss.org/mailman/listinfo/cdi-dev <
> 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 at lists.jboss.org <mailto:cdi-dev at lists.jboss.org>
> > https://lists.jboss.org/mailman/listinfo/cdi-dev <
> https://lists.jboss.org/mailman/listinfo/cdi-dev>
> >
> > _______________________________________________
> > cdi-dev mailing list
> > cdi-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/cdi-dev
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://lists.jboss.org/pipermail/cdi-dev/attachments/20140827/0e1e9a8b/attachment-0001.html
>
> ------------------------------
>
> Message: 2
> Date: Wed, 27 Aug 2014 12:37:10 +0200
> From: Antoine Sabot-Durand <antoine at sabot-durand.net>
> Subject: Re: [cdi-dev] Introduce myself
> To: Antonio Goncalves <antonio.goncalves at gmail.com>
> Cc: cdi-dev <cdi-dev at lists.jboss.org>
> Message-ID: <0546363E-823A-4B7B-95F0-27D872D171A3 at sabot-durand.net>
> Content-Type: text/plain; charset="utf-8"
>
> 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 at 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 at sabot-durand.net <mailto:antoine at 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/ <
> 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 at gmail.com <mailto:
> omeuefilipe at 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 at lists.jboss.org <mailto:cdi-dev at lists.jboss.org>
> >> https://lists.jboss.org/mailman/listinfo/cdi-dev <
> https://lists.jboss.org/mailman/listinfo/cdi-dev>
> >
> > _______________________________________________
> > cdi-dev mailing list
> > cdi-dev at lists.jboss.org <mailto:cdi-dev at lists.jboss.org>
> > https://lists.jboss.org/mailman/listinfo/cdi-dev <
> 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/5f53053b/attachment-0001.html
>
> ------------------------------
>
> Message: 3
> Date: Wed, 27 Aug 2014 12:46:03 +0200
> From: Antoine Sabot-Durand <antoine at sabot-durand.net>
> Subject: [cdi-dev] More info on EG application
> To: cdi-dev <cdi-dev at lists.jboss.org>
> Message-ID: <C7C48CBC-753D-41AC-BEFE-2623437AE5A9 at sabot-durand.net>
> Content-Type: text/plain; charset="utf-8"
>
> Hi all,
>
>
> Just to let you know that you can apply to the Expert Group on the JCP
> site (Remember that it?s not mandatory to be part o the project).
>
> To do so, you?ll have to be a JCP member. If you are not a jcp member yet
> check the info here : https://jcp.org/en/participation/membership <
> https://jcp.org/en/participation/membership>
> When ready you can apply to JSR 365 EG from the specification page :
> https://jcp.org/en/jsr/detail?id=365 <https://jcp.org/en/jsr/detail?id=365
> >
>
> We already have accepted 5 EG applications. The JCP organisation (PMO) has
> still to validate them, that?s why they are not visible in the EG yet.
>
> Antoine
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://lists.jboss.org/pipermail/cdi-dev/attachments/20140827/4968b47b/attachment-0001.html
>
> ------------------------------
>
> Message: 4
> Date: Wed, 27 Aug 2014 07:03:08 -0400
> From: "John D. Ament" <john.d.ament at gmail.com>
> Subject: Re: [cdi-dev] Introduce myself
> To: cdi-dev <cdi-dev at lists.jboss.org>
> Message-ID:
>         <
> CAOqetn858KEPudxHqSCgLkYj7W6SdmZUSQBpn8YD+_7fDH3hDw at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> 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 at 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 at 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 at 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 at 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 at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/cdi-dev
> >>
> >>
> >>
> >> _______________________________________________
> >> cdi-dev mailing list
> >> cdi-dev at 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 at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/cdi-dev
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://lists.jboss.org/pipermail/cdi-dev/attachments/20140827/57795157/attachment.html
>
> ------------------------------
>
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev
>
> End of cdi-dev Digest, Vol 45, Issue 10
> ***************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20140827/7004e06b/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 257 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/cdi-dev/attachments/20140827/7004e06b/attachment-0001.gif 

From thomas.pepio at gmail.com  Wed Aug 27 07:50:15 2014
From: thomas.pepio at gmail.com (Thomas Pepio)
Date: Wed, 27 Aug 2014 13:50:15 +0200
Subject: [cdi-dev] Introduce myself
In-Reply-To: <CAOqetn858KEPudxHqSCgLkYj7W6SdmZUSQBpn8YD+_7fDH3hDw@mail.gmail.com>
References: <CAKwwkgSK0T8n+nf+3t6PyHk4omkdvTgS7n2d3zZEg=+FwN3zuA@mail.gmail.com>
	<E2CD5830-179A-47D0-A636-6AA87FF159EA@sabot-durand.net>
	<CA+ZZq9_V5oSZ0QLpaDwhfvXjzrF6Gapjmf=yQX27=FJ+GdHN7Q@mail.gmail.com>
	<0546363E-823A-4B7B-95F0-27D872D171A3@sabot-durand.net>
	<CAOqetn858KEPudxHqSCgLkYj7W6SdmZUSQBpn8YD+_7fDH3hDw@mail.gmail.com>
Message-ID: <CAGDmESt9h02Ag_gWYgKLLjnyVh2RwjDv=HTRtq5W5zAPJM5ORQ@mail.gmail.com>

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 at 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 at 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 at 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 at 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 at 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 at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/cdi-dev
>>>
>>>
>>>
>>> _______________________________________________
>>> cdi-dev mailing list
>>> cdi-dev at 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 at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/cdi-dev
>>
>
>
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20140827/d41c341f/attachment.html 

From omeuefilipe at gmail.com  Wed Aug 27 07:59:10 2014
From: omeuefilipe at gmail.com (Filipe Portes)
Date: Wed, 27 Aug 2014 08:59:10 -0300
Subject: [cdi-dev] Introduce myself
In-Reply-To: <CAGDmESt9h02Ag_gWYgKLLjnyVh2RwjDv=HTRtq5W5zAPJM5ORQ@mail.gmail.com>
References: <CAKwwkgSK0T8n+nf+3t6PyHk4omkdvTgS7n2d3zZEg=+FwN3zuA@mail.gmail.com>
	<E2CD5830-179A-47D0-A636-6AA87FF159EA@sabot-durand.net>
	<CA+ZZq9_V5oSZ0QLpaDwhfvXjzrF6Gapjmf=yQX27=FJ+GdHN7Q@mail.gmail.com>
	<0546363E-823A-4B7B-95F0-27D872D171A3@sabot-durand.net>
	<CAOqetn858KEPudxHqSCgLkYj7W6SdmZUSQBpn8YD+_7fDH3hDw@mail.gmail.com>
	<CAGDmESt9h02Ag_gWYgKLLjnyVh2RwjDv=HTRtq5W5zAPJM5ORQ@mail.gmail.com>
Message-ID: <CAKwwkgSS4v1FdiL2-=M4T8b0wdwpOPa+aN7CSepEdALo1nNSCg@mail.gmail.com>

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 at 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 at 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 at 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 at 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 at 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 at 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 at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/cdi-dev
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> cdi-dev mailing list
>>>> cdi-dev at 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 at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/cdi-dev
>>>
>>
>>
>> _______________________________________________
>> cdi-dev mailing list
>> cdi-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/cdi-dev
>>
>
>
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20140827/322455d6/attachment.html 

From antonio.goncalves at gmail.com  Wed Aug 27 08:21:02 2014
From: antonio.goncalves at gmail.com (Antonio Goncalves)
Date: Wed, 27 Aug 2014 14:21:02 +0200
Subject: [cdi-dev] Introduce myself
In-Reply-To: <CAKwwkgSS4v1FdiL2-=M4T8b0wdwpOPa+aN7CSepEdALo1nNSCg@mail.gmail.com>
References: <CAKwwkgSK0T8n+nf+3t6PyHk4omkdvTgS7n2d3zZEg=+FwN3zuA@mail.gmail.com>
	<E2CD5830-179A-47D0-A636-6AA87FF159EA@sabot-durand.net>
	<CA+ZZq9_V5oSZ0QLpaDwhfvXjzrF6Gapjmf=yQX27=FJ+GdHN7Q@mail.gmail.com>
	<0546363E-823A-4B7B-95F0-27D872D171A3@sabot-durand.net>
	<CAOqetn858KEPudxHqSCgLkYj7W6SdmZUSQBpn8YD+_7fDH3hDw@mail.gmail.com>
	<CAGDmESt9h02Ag_gWYgKLLjnyVh2RwjDv=HTRtq5W5zAPJM5ORQ@mail.gmail.com>
	<CAKwwkgSS4v1FdiL2-=M4T8b0wdwpOPa+aN7CSepEdALo1nNSCg@mail.gmail.com>
Message-ID: <CA+ZZq9_a5NW-t5+NbH7_Vox=6M0xUGgZoRyOogHde4KsYfNW=A@mail.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 at 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 at 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 at 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 at 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 at 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 at 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 at 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 at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/cdi-dev
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> cdi-dev mailing list
>>>>> cdi-dev at 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 at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/cdi-dev
>>>>
>>>
>>>
>>> _______________________________________________
>>> cdi-dev mailing list
>>> cdi-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/cdi-dev
>>>
>>
>>
>> _______________________________________________
>> cdi-dev mailing list
>> cdi-dev at 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 at 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/attachment-0001.html 

From antonio.goncalves at gmail.com  Wed Aug 27 08:36:02 2014
From: antonio.goncalves at gmail.com (Antonio Goncalves)
Date: Wed, 27 Aug 2014 14:36:02 +0200
Subject: [cdi-dev] More info on EG application
In-Reply-To: <C7C48CBC-753D-41AC-BEFE-2623437AE5A9@sabot-durand.net>
References: <C7C48CBC-753D-41AC-BEFE-2623437AE5A9@sabot-durand.net>
Message-ID: <CA+ZZq9-9_4t5x28epvJ+MU-_f4R0R69eo9fHPBtV7p=jAAJ6Cg@mail.gmail.com>

Done ;o)


On Wed, Aug 27, 2014 at 12:46 PM, Antoine Sabot-Durand <
antoine at sabot-durand.net> wrote:

> Hi all,
>
>
> Just to let you know that you can apply to the Expert Group on the JCP
> site (Remember that it?s not mandatory to be part o the project).
>
> To do so, you?ll have to be a JCP member. If you are not a jcp member yet
> check the info here : https://jcp.org/en/participation/membership
> When ready you can apply to JSR 365 EG from the specification page :
> https://jcp.org/en/jsr/detail?id=365
>
> We already have accepted 5 EG applications. The JCP organisation (PMO) has
> still to validate them, that?s why they are not visible in the EG yet.
>
> Antoine
>
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at 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/0edf6235/attachment.html 

From werner.keil at gmail.com  Wed Aug 27 08:46:46 2014
From: werner.keil at gmail.com (Werner Keil)
Date: Wed, 27 Aug 2014 14:46:46 +0200
Subject: [cdi-dev] cdi-dev Digest, Vol 45, Issue 12
In-Reply-To: <mailman.19805.1409142089.2342.cdi-dev@lists.jboss.org>
References: <mailman.19805.1409142089.2342.cdi-dev@lists.jboss.org>
Message-ID: <CAAGawe0fzG=127WboUGXHVtj5CbFNd3a9R4W93-CdWNRqQy9xQ@mail.gmail.com>

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 at lists.jboss.org> wrote:

> Send cdi-dev mailing list submissions to
>         cdi-dev at 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 at lists.jboss.org
>
> You can reach the person managing the list at
>         cdi-dev-owner at 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 at gmail.com>
> Subject: Re: [cdi-dev] Introduce myself
> To: Filipe Portes <omeuefilipe at gmail.com>
> Cc: cdi-dev <cdi-dev at lists.jboss.org>
> Message-ID:
>         <CA+ZZq9_a5NW-t5+NbH7_Vox=6M0xUGgZoRyOogHde4KsYfNW=
> A at 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 at 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 at 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 at 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 at 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 at 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 at 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 at 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 at lists.jboss.org
> >>>>> https://lists.jboss.org/mailman/listinfo/cdi-dev
> >>>>>
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> cdi-dev mailing list
> >>>>> cdi-dev at 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 at lists.jboss.org
> >>>> https://lists.jboss.org/mailman/listinfo/cdi-dev
> >>>>
> >>>
> >>>
> >>> _______________________________________________
> >>> cdi-dev mailing list
> >>> cdi-dev at lists.jboss.org
> >>> https://lists.jboss.org/mailman/listinfo/cdi-dev
> >>>
> >>
> >>
> >> _______________________________________________
> >> cdi-dev mailing list
> >> cdi-dev at 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 at 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/attachment.html
>
> ------------------------------
>
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at 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
> ***************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20140827/757aff15/attachment-0001.html 

From issues at jboss.org  Wed Aug 27 09:06:00 2014
From: issues at jboss.org (Lucas Ventura Carro (JIRA))
Date: Wed, 27 Aug 2014 09:06:00 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-455) Allow building of TypeLiteral's
 with dynamic types
In-Reply-To: <JIRA.12550351.1409144729000@Atlassian.JIRA>
References: <JIRA.12550351.1409144729000@Atlassian.JIRA>
	<JIRA.12550351.1409144729477@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12550351.1409144729000.11147.1409144760038@Atlassian.JIRA>

Lucas Ventura Carro created CDI-455:
---------------------------------------

             Summary: 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-with-guice/].



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Wed Aug 27 09:06:59 2014
From: issues at jboss.org (Lucas Ventura Carro (JIRA))
Date: Wed, 27 Aug 2014 09:06:59 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-455) Allow building of TypeLiteral's
 with dynamic types
In-Reply-To: <JIRA.12550351.1409144729000@Atlassian.JIRA>
References: <JIRA.12550351.1409144729000@Atlassian.JIRA>
	<JIRA.12550351.1409144729000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12550351.1409144729000.11156.1409144819549@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/CDI-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lucas Ventura Carro updated CDI-455:
------------------------------------
    Forum Reference: http://luisfsgoncalves.wordpress.com/2010/09/08/generic-bindings-with-guice/


> 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-with-guice/].



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Wed Aug 27 09:06:59 2014
From: issues at jboss.org (Lucas Ventura Carro (JIRA))
Date: Wed, 27 Aug 2014 09:06:59 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-455) Allow building of TypeLiteral's
 with dynamic types
In-Reply-To: <JIRA.12550351.1409144729000@Atlassian.JIRA>
References: <JIRA.12550351.1409144729000@Atlassian.JIRA>
	<JIRA.12550351.1409144729000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12550351.1409144729000.11157.1409144819666@Atlassian.JIRA>


     [ https://issues.jboss.org/browse/CDI-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lucas Ventura Carro updated CDI-455:
------------------------------------
    Forum Reference: http://lists.jboss.org/pipermail/cdi-dev/2014-August/005178.html  (was: http://luisfsgoncalves.wordpress.com/2010/09/08/generic-bindings-with-guice/)


> 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-with-guice/].



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From pmuir at redhat.com  Wed Aug 27 09:22:07 2014
From: pmuir at redhat.com (Pete Muir)
Date: Wed, 27 Aug 2014 14:22:07 +0100
Subject: [cdi-dev] Updated terms for using CDI resources
Message-ID: <F11AE10E-C282-401A-A297-584EC365B62C@redhat.com>

Hi all,

Antoine and I have worked with Red Hat legal to clarify and update the terms under which you interact with the CDI EG. The updated terms are:

> You should note that by using any of the communication mechanisms associated with CDI (including the mailing list, the JIRA issue tracker and the github repository) you agree that:
> 
> 	? for all code provided on this list, you are licensing the code under the Apache License, Version 2.
> 
> 	? for all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.


The Contribute page on www.cdi-spec.org is updated (http://www.cdi-spec.org/contribute/), as is the footer for the mailing list.

Pete

From pmuir at redhat.com  Wed Aug 27 09:27:31 2014
From: pmuir at redhat.com (Pete Muir)
Date: Wed, 27 Aug 2014 14:27:31 +0100
Subject: [cdi-dev] cdi-dev Digest, Vol 45, Issue 12
In-Reply-To: <CAAGawe0fzG=127WboUGXHVtj5CbFNd3a9R4W93-CdWNRqQy9xQ@mail.gmail.com>
References: <mailman.19805.1409142089.2342.cdi-dev@lists.jboss.org>
	<CAAGawe0fzG=127WboUGXHVtj5CbFNd3a9R4W93-CdWNRqQy9xQ@mail.gmail.com>
Message-ID: <A26ECC3F-E31E-4FAC-8215-967AED31B9F5@redhat.com>

I?ve created a new thread to discuss the terms under which you contribute to CDI.

For CDI the only reason to sign up on the JCP page is to be listed on the JCP page.

On 27 Aug 2014, at 13:46, Werner Keil <werner.keil at gmail.com> wrote:

> 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 at lists.jboss.org> wrote:
> Send cdi-dev mailing list submissions to
>         cdi-dev at 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 at lists.jboss.org
> 
> You can reach the person managing the list at
>         cdi-dev-owner at 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 at gmail.com>
> Subject: Re: [cdi-dev] Introduce myself
> To: Filipe Portes <omeuefilipe at gmail.com>
> Cc: cdi-dev <cdi-dev at lists.jboss.org>
> Message-ID:
>         <CA+ZZq9_a5NW-t5+NbH7_Vox=6M0xUGgZoRyOogHde4KsYfNW=A at 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 at 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 at 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 at 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 at 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 at 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 at 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 at 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 at lists.jboss.org
> >>>>> https://lists.jboss.org/mailman/listinfo/cdi-dev
> >>>>>
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> cdi-dev mailing list
> >>>>> cdi-dev at 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 at lists.jboss.org
> >>>> https://lists.jboss.org/mailman/listinfo/cdi-dev
> >>>>
> >>>
> >>>
> >>> _______________________________________________
> >>> cdi-dev mailing list
> >>> cdi-dev at lists.jboss.org
> >>> https://lists.jboss.org/mailman/listinfo/cdi-dev
> >>>
> >>
> >>
> >> _______________________________________________
> >> cdi-dev mailing list
> >> cdi-dev at 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 at 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/attachment.html
> 
> ------------------------------
> 
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at 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
> ***************************************
> 
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at 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.



From werner.keil at gmail.com  Wed Aug 27 10:14:29 2014
From: werner.keil at gmail.com (Werner Keil)
Date: Wed, 27 Aug 2014 16:14:29 +0200
Subject: [cdi-dev] cdi-dev Digest, Vol 45, Issue 12
In-Reply-To: <A26ECC3F-E31E-4FAC-8215-967AED31B9F5@redhat.com>
References: <mailman.19805.1409142089.2342.cdi-dev@lists.jboss.org>
	<CAAGawe0fzG=127WboUGXHVtj5CbFNd3a9R4W93-CdWNRqQy9xQ@mail.gmail.com>
	<A26ECC3F-E31E-4FAC-8215-967AED31B9F5@redhat.com>
Message-ID: <CAAGawe2unDCRULhoG-7PyBB-2bvKCkLbWoUkWJq6kBwX_=4r8A@mail.gmail.com>

Given, CDI has a very liberal contribution and licensing model that seems
accepted by everyone in the EC including Oracle (I asked the IP WG and
while many of them like Azul, etc. who have a strong opinion said, they
would do it differently, nobody said it's against the JSPA so it's fine;-)
I guess those who don't care about being listed on the EG page may also
join differently and contribute via GitHub?;-)

Werner

On Wed, Aug 27, 2014 at 3:27 PM, Pete Muir <pmuir at redhat.com> wrote:

> I?ve created a new thread to discuss the terms under which you contribute
> to CDI.
>
> For CDI the only reason to sign up on the JCP page is to be listed on the
> JCP page.
>
> On 27 Aug 2014, at 13:46, Werner Keil <werner.keil at gmail.com> wrote:
>
> > 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 at lists.jboss.org>
> wrote:
> > Send cdi-dev mailing list submissions to
> >         cdi-dev at 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 at lists.jboss.org
> >
> > You can reach the person managing the list at
> >         cdi-dev-owner at 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 at gmail.com>
> > Subject: Re: [cdi-dev] Introduce myself
> > To: Filipe Portes <omeuefilipe at gmail.com>
> > Cc: cdi-dev <cdi-dev at lists.jboss.org>
> > Message-ID:
> >         <CA+ZZq9_a5NW-t5+NbH7_Vox=6M0xUGgZoRyOogHde4KsYfNW=
> A at 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 at 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 at 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 at 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 at 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 at 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 at 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 at 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 at lists.jboss.org
> > >>>>> https://lists.jboss.org/mailman/listinfo/cdi-dev
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>> _______________________________________________
> > >>>>> cdi-dev mailing list
> > >>>>> cdi-dev at 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 at lists.jboss.org
> > >>>> https://lists.jboss.org/mailman/listinfo/cdi-dev
> > >>>>
> > >>>
> > >>>
> > >>> _______________________________________________
> > >>> cdi-dev mailing list
> > >>> cdi-dev at lists.jboss.org
> > >>> https://lists.jboss.org/mailman/listinfo/cdi-dev
> > >>>
> > >>
> > >>
> > >> _______________________________________________
> > >> cdi-dev mailing list
> > >> cdi-dev at 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 at 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/attachment.html
> >
> > ------------------------------
> >
> > _______________________________________________
> > cdi-dev mailing list
> > cdi-dev at 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
> > ***************************************
> >
> > _______________________________________________
> > cdi-dev mailing list
> > cdi-dev at 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/20140827/c190e8a8/attachment-0001.html 

From antoine at sabot-durand.net  Wed Aug 27 12:07:48 2014
From: antoine at sabot-durand.net (Antoine Sabot-Durand)
Date: Wed, 27 Aug 2014 18:07:48 +0200
Subject: [cdi-dev] Switching from old IRC channel : #jsr346 to #cdi-dev
Message-ID: <3C0F2174-4961-4F92-B7BE-06E2CB65A508@sabot-durand.net>

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

From antonio.goncalves at gmail.com  Wed Aug 27 14:33:39 2014
From: antonio.goncalves at gmail.com (Antonio Goncalves)
Date: Wed, 27 Aug 2014 20:33:39 +0200
Subject: [cdi-dev] Switching from old IRC channel : #jsr346 to #cdi-dev
In-Reply-To: <3C0F2174-4961-4F92-B7BE-06E2CB65A508@sabot-durand.net>
References: <3C0F2174-4961-4F92-B7BE-06E2CB65A508@sabot-durand.net>
Message-ID: <CA+ZZq9-zMHb30oapem9v3J-xg-DhrqJPTNaSvmpR8=KOqBXQTg@mail.gmail.com>

/join #cdi-dev
#cdi-dev :Cannot join channel (+r) - you need to be identified with services

Any idea ? I'm already part of #jsr346, #forge, #arquillian... and it works
fine.

Antonio


On Wed, Aug 27, 2014 at 6:07 PM, Antoine Sabot-Durand <
antoine at sabot-durand.net> wrote:

> 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
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at 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.
>



-- 
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/4a03fb5d/attachment.html 

From pmuir at redhat.com  Wed Aug 27 15:29:00 2014
From: pmuir at redhat.com (Pete Muir)
Date: Wed, 27 Aug 2014 20:29:00 +0100
Subject: [cdi-dev] Switching from old IRC channel : #jsr346 to #cdi-dev
In-Reply-To: <CA+ZZq9-zMHb30oapem9v3J-xg-DhrqJPTNaSvmpR8=KOqBXQTg@mail.gmail.com>
References: <3C0F2174-4961-4F92-B7BE-06E2CB65A508@sabot-durand.net>
	<CA+ZZq9-zMHb30oapem9v3J-xg-DhrqJPTNaSvmpR8=KOqBXQTg@mail.gmail.com>
Message-ID: <46C231B8-8307-4788-B54E-6CCC6D8B4CD0@redhat.com>

https://freenode.net/faq.shtml#plusr

On 27 Aug 2014, at 19:33, Antonio Goncalves <antonio.goncalves at gmail.com> wrote:

> /join #cdi-dev
> #cdi-dev :Cannot join channel (+r) - you need to be identified with services
> 
> Any idea ? I'm already part of #jsr346, #forge, #arquillian... and it works fine.
> 
> Antonio
> 
> 
> On Wed, Aug 27, 2014 at 6:07 PM, Antoine Sabot-Durand <antoine at sabot-durand.net> wrote:
> 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
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at 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.
> 
> 
> 
> -- 
> Antonio Goncalves 
> Software architect, Java Champion and Pluralsight author
> 
> Web site | Twitter | LinkedIn | Pluralsight | Paris JUG | Devoxx France
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at 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.



From antonio.goncalves at gmail.com  Wed Aug 27 16:52:13 2014
From: antonio.goncalves at gmail.com (Antonio Goncalves)
Date: Wed, 27 Aug 2014 22:52:13 +0200
Subject: [cdi-dev] Switching from old IRC channel : #jsr346 to #cdi-dev
In-Reply-To: <46C231B8-8307-4788-B54E-6CCC6D8B4CD0@redhat.com>
References: <3C0F2174-4961-4F92-B7BE-06E2CB65A508@sabot-durand.net>
	<CA+ZZq9-zMHb30oapem9v3J-xg-DhrqJPTNaSvmpR8=KOqBXQTg@mail.gmail.com>
	<46C231B8-8307-4788-B54E-6CCC6D8B4CD0@redhat.com>
Message-ID: <CA+ZZq980iF5jcjnRJ99G53yLax7B9gjON1B1Gdo8qTjuABf-Og@mail.gmail.com>

Done. Thanks

Antonio


On Wed, Aug 27, 2014 at 9:29 PM, Pete Muir <pmuir at redhat.com> wrote:

> https://freenode.net/faq.shtml#plusr
>
> On 27 Aug 2014, at 19:33, Antonio Goncalves <antonio.goncalves at gmail.com>
> wrote:
>
> > /join #cdi-dev
> > #cdi-dev :Cannot join channel (+r) - you need to be identified with
> services
> >
> > Any idea ? I'm already part of #jsr346, #forge, #arquillian... and it
> works fine.
> >
> > Antonio
> >
> >
> > On Wed, Aug 27, 2014 at 6:07 PM, Antoine Sabot-Durand <
> antoine at sabot-durand.net> wrote:
> > 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
> > _______________________________________________
> > cdi-dev mailing list
> > cdi-dev at 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.
> >
> >
> >
> > --
> > Antonio Goncalves
> > Software architect, Java Champion and Pluralsight author
> >
> > Web site | Twitter | LinkedIn | Pluralsight | Paris JUG | Devoxx France
> > _______________________________________________
> > cdi-dev mailing list
> > cdi-dev at 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.
>
>


-- 
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/9fadfc6c/attachment.html 

From issues at jboss.org  Thu Aug 28 05:12:59 2014
From: issues at jboss.org (Lucas Ventura Carro (JIRA))
Date: Thu, 28 Aug 2014 05:12:59 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-455) Allow building of TypeLiteral's
 with dynamic types
In-Reply-To: <JIRA.12550351.1409144729000@Atlassian.JIRA>
References: <JIRA.12550351.1409144729000@Atlassian.JIRA>
	<JIRA.12550351.1409144729000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12550351.1409144729000.13249.1409217179950@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/CDI-455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996376#comment-12996376 ] 

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-with-guice/], 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-with-guice/].



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From issues at jboss.org  Thu Aug 28 05:13:00 2014
From: issues at jboss.org (Lucas Ventura Carro (JIRA))
Date: Thu, 28 Aug 2014 05:13:00 -0400 (EDT)
Subject: [cdi-dev] [JBoss JIRA] (CDI-455) Allow building of TypeLiteral's
 with dynamic types
In-Reply-To: <JIRA.12550351.1409144729000@Atlassian.JIRA>
References: <JIRA.12550351.1409144729000@Atlassian.JIRA>
	<JIRA.12550351.1409144729000@jira02.app.mwc.hst.phx2.redhat.com>
Message-ID: <JIRA.12550351.1409144729000.13250.1409217180185@Atlassian.JIRA>


    [ https://issues.jboss.org/browse/CDI-455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12996376#comment-12996376 ] 

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-with-guice/], 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-with-guice/], 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-with-guice/].



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)

From antoine at sabot-durand.net  Fri Aug 29 05:49:08 2014
From: antoine at sabot-durand.net (Antoine Sabot-Durand)
Date: Fri, 29 Aug 2014 11:49:08 +0200
Subject: [cdi-dev] Working method for CDI 2.0 (a proposal)
Message-ID: <20396F96-ACC0-4DF5-A774-245D93495485@sabot-durand.net>

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20140829/cf706814/attachment-0001.html 

From pmuir at redhat.com  Fri Aug 29 07:19:43 2014
From: pmuir at redhat.com (Pete Muir)
Date: Fri, 29 Aug 2014 12:19:43 +0100
Subject: [cdi-dev] Working method for CDI 2.0 (a proposal)
In-Reply-To: <20396F96-ACC0-4DF5-A774-245D93495485@sabot-durand.net>
References: <20396F96-ACC0-4DF5-A774-245D93495485@sabot-durand.net>
Message-ID: <082E6FF7-2A74-4ACB-9C50-00B6F99AB3C4@redhat.com>

Looks like a good approach to me.

On 29 Aug 2014, at 10:49, Antoine Sabot-Durand <antoine at sabot-durand.net> wrote:

> 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
> 
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at 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.



From antonin at stefanutti.fr  Fri Aug 29 08:07:27 2014
From: antonin at stefanutti.fr (Antonin Stefanutti)
Date: Fri, 29 Aug 2014 12:07:27 +0000
Subject: [cdi-dev] Working method for CDI 2.0 (a proposal)
In-Reply-To: <082E6FF7-2A74-4ACB-9C50-00B6F99AB3C4@redhat.com>
References: <20396F96-ACC0-4DF5-A774-245D93495485@sabot-durand.net>,
	<082E6FF7-2A74-4ACB-9C50-00B6F99AB3C4@redhat.com>
Message-ID: <7b5b1a0127064c2b85644309e3ae29d5@MBX003.indiv.local>

Hi Antoine,

I think that's a great plan!

For <SPI enhancement for integration>, container monitoring could be considered. For <Java 8 enhancement>, I'd add parameter names support. And for <Interceptor & Decorator> we may want to revise the proxying strategies / limitations.

Can't wait to get started.

Antonin
________________________________________
From: cdi-dev-bounces at lists.jboss.org <cdi-dev-bounces at lists.jboss.org> on behalf of Pete Muir <pmuir at redhat.com>
Sent: Friday, August 29, 2014 1:19 PM
To: Antoine Sabot-Durand
Cc: cdi-dev
Subject: Re: [cdi-dev] Working method for CDI 2.0 (a proposal)

Looks like a good approach to me.

On 29 Aug 2014, at 10:49, Antoine Sabot-Durand <antoine at sabot-durand.net> wrote:

> 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
>
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at 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 at 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.


From antoine at sabot-durand.net  Fri Aug 29 09:32:37 2014
From: antoine at sabot-durand.net (Antoine Sabot-Durand)
Date: Fri, 29 Aug 2014 15:32:37 +0200
Subject: [cdi-dev] Spec launch meeting and CDI weekly meeting
Message-ID: <EA5490D7-1F15-414B-91D1-88BCFD9FC845@sabot-durand.net>

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20140829/b2e4be7a/attachment.html 

From antoine at sabot-durand.net  Fri Aug 29 10:08:22 2014
From: antoine at sabot-durand.net (Antoine Sabot-Durand)
Date: Fri, 29 Aug 2014 16:08:22 +0200
Subject: [cdi-dev] EG membership status
Message-ID: <B5089D59-C0A4-448D-A934-028CE44C2804@sabot-durand.net>

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


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20140829/d1a94f75/attachment.html 

From john.d.ament at gmail.com  Fri Aug 29 11:49:44 2014
From: john.d.ament at gmail.com (John D. Ament)
Date: Fri, 29 Aug 2014 11:49:44 -0400
Subject: [cdi-dev] EG membership status
In-Reply-To: <B5089D59-C0A4-448D-A934-028CE44C2804@sabot-durand.net>
References: <B5089D59-C0A4-448D-A934-028CE44C2804@sabot-durand.net>
Message-ID: <CAOqetn-DH4v_jC83rXkHc8B01N_3v9TAN9p4+843b6PHwYp5BQ@mail.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 at 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 at 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/8a774675/attachment-0001.html 

From john.d.ament at gmail.com  Fri Aug 29 12:53:10 2014
From: john.d.ament at gmail.com (John D. Ament)
Date: Fri, 29 Aug 2014 12:53:10 -0400
Subject: [cdi-dev] Spec launch meeting and CDI weekly meeting
In-Reply-To: <EA5490D7-1F15-414B-91D1-88BCFD9FC845@sabot-durand.net>
References: <EA5490D7-1F15-414B-91D1-88BCFD9FC845@sabot-durand.net>
Message-ID: <CAOqetn_qPbZFExnhP0MZ1DTMYYmc52yz7rjCLSDYzN_b_R+Kdg@mail.gmail.com>

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 at 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 at 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/attachment.html 

From thjanssen123 at gmail.com  Fri Aug 29 15:17:09 2014
From: thjanssen123 at gmail.com (Thorben Janssen)
Date: Fri, 29 Aug 2014 21:17:09 +0200
Subject: [cdi-dev] Introduce myself
In-Reply-To: <CA+ZZq9_a5NW-t5+NbH7_Vox=6M0xUGgZoRyOogHde4KsYfNW=A@mail.gmail.com>
References: <CAKwwkgSK0T8n+nf+3t6PyHk4omkdvTgS7n2d3zZEg=+FwN3zuA@mail.gmail.com>
	<E2CD5830-179A-47D0-A636-6AA87FF159EA@sabot-durand.net>
	<CA+ZZq9_V5oSZ0QLpaDwhfvXjzrF6Gapjmf=yQX27=FJ+GdHN7Q@mail.gmail.com>
	<0546363E-823A-4B7B-95F0-27D872D171A3@sabot-durand.net>
	<CAOqetn858KEPudxHqSCgLkYj7W6SdmZUSQBpn8YD+_7fDH3hDw@mail.gmail.com>
	<CAGDmESt9h02Ag_gWYgKLLjnyVh2RwjDv=HTRtq5W5zAPJM5ORQ@mail.gmail.com>
	<CAKwwkgSS4v1FdiL2-=M4T8b0wdwpOPa+aN7CSepEdALo1nNSCg@mail.gmail.com>
	<CA+ZZq9_a5NW-t5+NbH7_Vox=6M0xUGgZoRyOogHde4KsYfNW=A@mail.gmail.com>
Message-ID: <CAE9nDy9m-euJ7DoiyS9_KD3JXXF10Jv9Z1pRqVH1OcTzYkE+aA@mail.gmail.com>

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 at 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 at 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 at 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 at 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 at 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 at 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 at 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 at 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 at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/cdi-dev
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> cdi-dev mailing list
>>>>>> cdi-dev at 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 at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/cdi-dev
>>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> cdi-dev mailing list
>>>> cdi-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/cdi-dev
>>>>
>>>
>>>
>>> _______________________________________________
>>> cdi-dev mailing list
>>> cdi-dev at 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 at 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 at 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/attachment.html 

From thjanssen123 at gmail.com  Fri Aug 29 15:36:51 2014
From: thjanssen123 at gmail.com (Thorben Janssen)
Date: Fri, 29 Aug 2014 21:36:51 +0200
Subject: [cdi-dev] EG membership status
In-Reply-To: <CAOqetn-DH4v_jC83rXkHc8B01N_3v9TAN9p4+843b6PHwYp5BQ@mail.gmail.com>
References: <B5089D59-C0A4-448D-A934-028CE44C2804@sabot-durand.net>
	<CAOqetn-DH4v_jC83rXkHc8B01N_3v9TAN9p4+843b6PHwYp5BQ@mail.gmail.com>
Message-ID: <CAE9nDy8Lxo1pFzxE_mWEPwS9KZ+RE0+0Gm4mVeMYYT3n7Y6STg@mail.gmail.com>

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 at 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 at 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 at 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 at 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/attachment-0001.html 

From werner.keil at gmail.com  Fri Aug 29 16:00:34 2014
From: werner.keil at gmail.com (Werner Keil)
Date: Fri, 29 Aug 2014 22:00:34 +0200
Subject: [cdi-dev] cdi-dev Digest, Vol 45, Issue 17
In-Reply-To: <mailman.21439.1409341017.2342.cdi-dev@lists.jboss.org>
References: <mailman.21439.1409341017.2342.cdi-dev@lists.jboss.org>
Message-ID: <CAAGawe1HPc3d1eb3Uo5+S6jBw6h4O7Z3pKcvKVDeQcJqnbomiA@mail.gmail.com>

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 at lists.jboss.org> wrote:

> Send cdi-dev mailing list submissions to
>         cdi-dev at 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 at lists.jboss.org
>
> You can reach the person managing the list at
>         cdi-dev-owner at 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 at gmail.com>
> Subject: Re: [cdi-dev] Spec launch meeting and CDI weekly meeting
> To: Antoine Sabot-Durand <antoine at sabot-durand.net>
> Cc: cdi-dev <cdi-dev at lists.jboss.org>
> Message-ID:
>         <
> CAOqetn_qPbZFExnhP0MZ1DTMYYmc52yz7rjCLSDYzN_b_R+Kdg at 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 at 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 at 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/attachment-0001.html
>
> ------------------------------
>
> Message: 2
> Date: Fri, 29 Aug 2014 21:17:09 +0200
> From: Thorben Janssen <thjanssen123 at gmail.com>
> Subject: Re: [cdi-dev] Introduce myself
> To: cdi-dev <cdi-dev at lists.jboss.org>
> Message-ID:
>         <
> CAE9nDy9m-euJ7DoiyS9_KD3JXXF10Jv9Z1pRqVH1OcTzYkE+aA at 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 at 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 at 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 at 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 at 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 at 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 at 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 at 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 at 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 at lists.jboss.org
> >>>>>> https://lists.jboss.org/mailman/listinfo/cdi-dev
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> cdi-dev mailing list
> >>>>>> cdi-dev at 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 at lists.jboss.org
> >>>>> https://lists.jboss.org/mailman/listinfo/cdi-dev
> >>>>>
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> cdi-dev mailing list
> >>>> cdi-dev at lists.jboss.org
> >>>> https://lists.jboss.org/mailman/listinfo/cdi-dev
> >>>>
> >>>
> >>>
> >>> _______________________________________________
> >>> cdi-dev mailing list
> >>> cdi-dev at 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 at 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 at 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/attachment-0001.html
>
> ------------------------------
>
> Message: 3
> Date: Fri, 29 Aug 2014 21:36:51 +0200
> From: Thorben Janssen <thjanssen123 at gmail.com>
> Subject: Re: [cdi-dev] EG membership status
> To: "John D. Ament" <john.d.ament at gmail.com>
> Cc: cdi-dev <cdi-dev at lists.jboss.org>
> Message-ID:
>         <
> CAE9nDy8Lxo1pFzxE_mWEPwS9KZ+RE0+0Gm4mVeMYYT3n7Y6STg at 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 at 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 at 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 at 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 at 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/attachment.html
>
> ------------------------------
>
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at 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
> ***************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20140829/f73e4f95/attachment-0001.html 

From antoine at sabot-durand.net  Sat Aug 30 06:17:58 2014
From: antoine at sabot-durand.net (Antoine Sabot-Durand)
Date: Sat, 30 Aug 2014 12:17:58 +0200
Subject: [cdi-dev] Spec launch meeting and CDI weekly meeting
In-Reply-To: <CAOqetn_qPbZFExnhP0MZ1DTMYYmc52yz7rjCLSDYzN_b_R+Kdg@mail.gmail.com>
References: <EA5490D7-1F15-414B-91D1-88BCFD9FC845@sabot-durand.net>
	<CAOqetn_qPbZFExnhP0MZ1DTMYYmc52yz7rjCLSDYzN_b_R+Kdg@mail.gmail.com>
Message-ID: <B8A699E6-AAEF-4E5F-8291-E0E4F687C301@sabot-durand.net>

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 at 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 at sabot-durand.net <mailto:antoine at 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 <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 at lists.jboss.org <mailto:cdi-dev at 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/20140830/a101a985/attachment.html 

From thjanssen123 at gmail.com  Sat Aug 30 06:53:12 2014
From: thjanssen123 at gmail.com (Thorben Janssen)
Date: Sat, 30 Aug 2014 12:53:12 +0200
Subject: [cdi-dev] Spec launch meeting and CDI weekly meeting
Message-ID: <5401ae92.0153b40a.4f24.ffff9183@mx.google.com>

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 at sabot-durand.net>
Gesendet: ?30.?08.?2014 12:18
An: "John D. Ament" <john.d.ament at gmail.com>
Cc: "cdi-dev" <cdi-dev at 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 at 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 at 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 at 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/20140830/21a116b0/attachment.html 

From mpaluch at paluch.biz  Sat Aug 30 08:00:15 2014
From: mpaluch at paluch.biz (Mark Paluch)
Date: Sat, 30 Aug 2014 14:00:15 +0200
Subject: [cdi-dev] Spec launch meeting and CDI weekly meeting
In-Reply-To: <5401ae92.0153b40a.4f24.ffff9183@mx.google.com>
References: <5401ae92.0153b40a.4f24.ffff9183@mx.google.com>
Message-ID: <CAA49CD3-C85F-4829-92AC-22195B79ED74@paluch.biz>

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 at 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 <mailto:antoine at sabot-durand.net>
> Gesendet: ?30.?08.?2014 12:18
> An: John D. Ament <mailto:john.d.ament at gmail.com>
> Cc: cdi-dev <mailto:cdi-dev at 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 at gmail.com <mailto:john.d.ament at 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 at sabot-durand.net <mailto:antoine at 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 <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 at lists.jboss.org <mailto:cdi-dev at 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 at 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/20140830/27245aa9/attachment-0001.html