<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Hi Stephan,</div><div class=""><br class=""></div><div class="">I am suggesting that JSR-330 gets rolled into the CDI spec as a chapter as it currently</div><div class="">stands. Anything beyond that is beyond the scope of the discussion/wish I have as that</div><div class="">would then be decided by the combined EG.</div><div class=""><br class=""></div><div class="">Thanks!</div><div class=""><br class=""></div><div class="">King regards,</div><div class="">Manfred Riem</div><div class=""><br class=""></div><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 19, 2016, at 2:33 PM, Stephan Knitelius <<a href="mailto:stephan@knitelius.com" class="">stephan@knitelius.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div style="white-space:pre-wrap" class="">If I understand you correctly, you are suggesting to move the JSR-330 annotations into a separate CDI module/profile, thereby semi-deprecating these.<br class=""><br class="">This would essentially open up the possibility of replacing @Named, etc... with CDI specific annotations.<br class=""><br class="">Certainly an interesting path to explore. <br class=""><br class="">Stephan<br class=""><br class=""></div><br class=""><div class="gmail_quote"><div dir="ltr" class="">On Sa., 19. März 2016 at 19:27, Manfred Riem <<a href="mailto:mnriem@gmail.com" class="">mnriem@gmail.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I couldn't agree more ;)<br class="">
<br class="">
Thanks!<br class="">
<br class="">
Kind regards,<br class="">
Manfred Riem<br class="">
<br class="">
> On Mar 19, 2016, at 10:47 AM, Reza Rahman <<a href="mailto:reza_rahman@lycos.com" target="_blank" class="">reza_rahman@lycos.com</a>> wrote:<br class="">
><br class="">
> I definitely think it's an idea worth exploring. It will strengthen CDI's hand further. It will be great if some of the confusingly redundant APIs like @Singleton could be deprecated in the process.<br class="">
><br class="">
> BTW, it is really great to see you active in the community!<br class="">
><br class="">
>> On Mar 19, 2016, at 10:49 AM, Manfred Riem <<a href="mailto:mnriem@gmail.com" target="_blank" class="">mnriem@gmail.com</a>> wrote:<br class="">
>><br class="">
>> Hi all,<br class="">
>><br class="">
>> I wrote a little blog entry about a CDI wish I have and in essence it comes<br class="">
>> down to merging JSR-330 into the CDI specification as a sub spec. I realize<br class="">
>> there is history there, but to me it looks like the best course of action.<br class="">
>><br class="">
>> I had some twitter exchanges about this and some folks are for, some are<br class="">
>> against.<br class="">
>><br class="">
>> Note I think this is worth exploring as an idea, not something that<br class="">
>> necessarily needs to be in the current JSR, but definitely something that I<br class="">
>> think is worth to do at some point (sooner rather than later in my book).<br class="">
>><br class="">
>> What do you think?<br class="">
>><br class="">
>> Thanks!<br class="">
>><br class="">
>> Kind regards,<br class="">
>> Manfred Riem<br class="">
>><br class="">
>><br class="">
>><br class="">
>> --<br class="">
>> View this message in context: <a href="http://cdi-development-mailing-list.1064426.n5.nabble.com/Merging-JSR-330-into-CDI-tp5712810.html" rel="noreferrer" target="_blank" class="">http://cdi-development-mailing-list.1064426.n5.nabble.com/Merging-JSR-330-into-CDI-tp5712810.html</a><br class="">
>> Sent from the CDI Development mailing list mailing list archive at <a href="http://nabble.com" class="">Nabble.com</a>.<br class="">
>> _______________________________________________<br class="">
>> cdi-dev mailing list<br class="">
>> <a href="mailto:cdi-dev@lists.jboss.org" target="_blank" class="">cdi-dev@lists.jboss.org</a><br class="">
>> <a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" rel="noreferrer" target="_blank" class="">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br class="">
>><br class="">
>> Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 (<a href="http://www.apache.org/licenses/LICENSE-2.0.html" rel="noreferrer" target="_blank" class="">http://www.apache.org/licenses/LICENSE-2.0.html</a>). For all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.<br class="">
><br class="">
> _______________________________________________<br class="">
> cdi-dev mailing list<br class="">
> <a href="mailto:cdi-dev@lists.jboss.org" target="_blank" class="">cdi-dev@lists.jboss.org</a><br class="">
> <a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" rel="noreferrer" target="_blank" class="">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br class="">
><br class="">
> Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 (<a href="http://www.apache.org/licenses/LICENSE-2.0.html" rel="noreferrer" target="_blank" class="">http://www.apache.org/licenses/LICENSE-2.0.html</a>). For all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.<br class="">
<br class="">
_______________________________________________<br class="">
cdi-dev mailing list<br class="">
<a href="mailto:cdi-dev@lists.jboss.org" target="_blank" class="">cdi-dev@lists.jboss.org</a><br class="">
<a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" rel="noreferrer" target="_blank" class="">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br class="">
<br class="">
Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 (<a href="http://www.apache.org/licenses/LICENSE-2.0.html" rel="noreferrer" target="_blank" class="">http://www.apache.org/licenses/LICENSE-2.0.html</a>). For all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.<br class="">
</blockquote></div>
</div></blockquote></div><br class=""></body></html>