Hi Manfred,<br><br>sorry my replay was a bit out of context since, I was referring to Rezas last mail.<br><br>As already discussed yesterday, this could proof difficult. Since there are other implementations based on JSR-330, most noticeably spring. <br><br>What exactly are we looking to gain from integrating JSR-330?<br><br>I agree it would be "cleaner", but maybe too much effort for too little gain.<br><br>If we wanted greater control over those parts, maybe it would be better to move these parts into a separate module for backwards compatibility.<br>Including new CDI owned annotations alongside the separated JSR-330, as and where sensible.<br><br>Stephan <br><br><br><div class="gmail_quote"><div dir="ltr">On Sa., 19. März 2016 at 20:40, Manfred Riem <<a href="mailto:mnriem@gmail.com">mnriem@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>Hi Stephan,</div><div><br></div><div>I am suggesting that JSR-330 gets rolled into the CDI spec as a chapter as it currently</div><div>stands. Anything beyond that is beyond the scope of the discussion/wish I have as that</div><div>would then be decided by the combined EG.</div><div><br></div><div>Thanks!</div><div><br></div><div>King regards,</div><div>Manfred Riem</div></div><div style="word-wrap:break-word"><div><br></div><br><div><blockquote type="cite"><div>On Mar 19, 2016, at 2:33 PM, Stephan Knitelius <<a href="mailto:stephan@knitelius.com" target="_blank">stephan@knitelius.com</a>> wrote:</div><br><div><div style="white-space:pre-wrap">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><br>This would essentially open up the possibility of replacing @Named, etc... with CDI specific annotations.<br><br>Certainly an interesting path to explore. <br><br>Stephan<br><br></div><br><div class="gmail_quote"><div dir="ltr">On Sa., 19. März 2016 at 19:27, Manfred Riem <<a href="mailto:mnriem@gmail.com" target="_blank">mnriem@gmail.com</a>> wrote:<br></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>
<br>
Thanks!<br>
<br>
Kind regards,<br>
Manfred Riem<br>
<br>
> On Mar 19, 2016, at 10:47 AM, Reza Rahman <<a href="mailto:reza_rahman@lycos.com" target="_blank">reza_rahman@lycos.com</a>> wrote:<br>
><br>
> 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>
><br>
> BTW, it is really great to see you active in the community!<br>
><br>
>> On Mar 19, 2016, at 10:49 AM, Manfred Riem <<a href="mailto:mnriem@gmail.com" target="_blank">mnriem@gmail.com</a>> wrote:<br>
>><br>
>> Hi all,<br>
>><br>
>> I wrote a little blog entry about a CDI wish I have and in essence it comes<br>
>> down to merging JSR-330 into the CDI specification as a sub spec. I realize<br>
>> there is history there, but to me it looks like the best course of action.<br>
>><br>
>> I had some twitter exchanges about this and some folks are for, some are<br>
>> against.<br>
>><br>
>> Note I think this is worth exploring as an idea, not something that<br>
>> necessarily needs to be in the current JSR, but definitely something that I<br>
>> think is worth to do at some point (sooner rather than later in my book).<br>
>><br>
>> What do you think?<br>
>><br>
>> Thanks!<br>
>><br>
>> Kind regards,<br>
>> Manfred Riem<br>
>><br>
>><br>
>><br>
>> --<br>
>> 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">http://cdi-development-mailing-list.1064426.n5.nabble.com/Merging-JSR-330-into-CDI-tp5712810.html</a><br>
>> Sent from the CDI Development mailing list mailing list archive at <a href="http://nabble.com" target="_blank">Nabble.com</a>.<br>
>> _______________________________________________<br>
>> cdi-dev mailing list<br>
>> <a href="mailto:cdi-dev@lists.jboss.org" target="_blank">cdi-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
>><br>
>> 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">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>
><br>
> _______________________________________________<br>
> cdi-dev mailing list<br>
> <a href="mailto:cdi-dev@lists.jboss.org" target="_blank">cdi-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
><br>
> 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">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>
<br>
_______________________________________________<br>
cdi-dev mailing list<br>
<a href="mailto:cdi-dev@lists.jboss.org" target="_blank">cdi-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
<br>
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">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>
</blockquote></div>
</div></blockquote></div><br></div></blockquote></div>