[cdi-dev] Merging JSR-330 into CDI

Stephan Knitelius stephan at knitelius.com
Sat Mar 19 15:33:48 EDT 2016


If I understand you correctly, you are suggesting to move the JSR-330
annotations into a separate CDI module/profile, thereby semi-deprecating
these.

This would essentially open up the possibility of replacing @Named, etc...
with CDI specific annotations.

Certainly an interesting path to explore.

Stephan


On Sa., 19. März 2016 at 19:27, Manfred Riem <mnriem at gmail.com> wrote:

> I couldn't agree more ;)
>
> Thanks!
>
> Kind regards,
> Manfred Riem
>
> > On Mar 19, 2016, at 10:47 AM, Reza Rahman <reza_rahman at lycos.com> wrote:
> >
> > 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 at 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-into-CDI-tp5712810.html
> >> Sent from the CDI Development mailing list mailing list archive at
> Nabble.com.
> >> _______________________________________________
> >> 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.
>
> _______________________________________________
> 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/20160319/5c56b90a/attachment.html 


More information about the cdi-dev mailing list