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.
BTW, it is really great to see you active in the community!
On Mar 19, 2016, at 10:49 AM, Manfred Riem <mnriem(a)gmail.com>
wrote:
Hi all,
I wrote a little blog entry about a CDI wish I have and in essence it comes
down to merging JSR-330 into the CDI specification as a sub spec. I realize
there is history there, but to me it looks like the best course of action.
I had some twitter exchanges about this and some folks are for, some are
against.
Note I think this is worth exploring as an idea, not something that
necessarily needs to be in the current JSR, but definitely something that I
think is worth to do at some point (sooner rather than later in my book).
What do you think?
Thanks!
Kind regards,
Manfred Riem
--
View this message in context:
http://cdi-development-mailing-list.1064426.n5.nabble.com/Merging-JSR-330...
Sent from the CDI Development mailing list mailing list archive at
Nabble.com.
_______________________________________________
cdi-dev mailing list
cdi-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/cdi-dev
Note that for all code provided on this list, the provider licenses the code under the
Apache License, Version 2 (
http://www.apache.org/licenses/LICENSE-2.0.html). For all other
ideas provided on this list, the provider waives all patent and other intellectual
property rights inherent in such information.