[cdi-dev] Merging JSR-330 into CDI

Sat Mar 19 16:44:29 EDT 2016

Hi,

On Saturday, March 19, 2016, Stephan Knitelius <stephan at knitelius.com>
wrote:

> Hi Manfred,
>
> sorry my replay was a bit out of context since, I was referring to Rezas
> last mail.
>
> As already discussed yesterday, this could proof difficult. Since there
> are other implementations based on JSR-330, most noticeably spring.

Wound anything really change for other implementations technically?

AtInject 1.0 will stay as it is, but newer versions of it will be done as
sub-spec of CDI, right?

If those other implementations do not want changes in AtInject then things
can stay as they are, and if they do want changes they can ask the CDI EG,
which is active.

If it's a sub-spec, I guess just the sub-spec can be officially implemented
(like Hibernate implemented just sub-spec JPA which was initially part of
EJB).

But have those other implementations ever asked for changes?

Kind regards,
Arjan Tijms

>
> What exactly are we looking to gain from integrating JSR-330?
>
> I agree it would be "cleaner", but maybe too much effort for too little
> gain.
>
> If we wanted greater control over those parts, maybe it would be better to
> move these parts into a separate module for backwards compatibility.
> Including new CDI owned annotations alongside the separated JSR-330, as
> and where sensible.
>
> Stephan
>
>
> On Sa., 19. März 2016 at 20:40, Manfred Riem <mnriem at gmail.com
> <javascript:_e(%7B%7D,'cvml','mnriem at gmail.com');>> wrote:
>
>> Hi Stephan,
>>
>> I am suggesting that JSR-330 gets rolled into the CDI spec as a chapter
>> as it currently
>> stands. Anything beyond that is beyond the scope of the discussion/wish I
>> have as that
>> would then be decided by the combined EG.
>>
>> Thanks!
>>
>> King regards,
>> Manfred Riem
>>
>>
>> On Mar 19, 2016, at 2:33 PM, Stephan Knitelius <stephan at knitelius.com
>> <javascript:_e(%7B%7D,'cvml','stephan at knitelius.com');>> wrote:
>>
>> 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
>> <javascript:_e(%7B%7D,'cvml','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
>>> <javascript:_e(%7B%7D,'cvml','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
>>> <javascript:_e(%7B%7D,'cvml','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 <http://nabble.com>.
>>> >> _______________________________________________
>>> >> cdi-dev mailing list
>>> >> cdi-dev at lists.jboss.org
>>> <javascript:_e(%7B%7D,'cvml','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
>>> <javascript:_e(%7B%7D,'cvml','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
>>> <javascript:_e(%7B%7D,'cvml','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/5ae8a87f/attachment.html 