[cdi-dev] Feedback from Devoxx

[arjan tijms]

On Tue, Nov 18, 2014 at 11:11 AM, Antoine Sabot-Durand
<antoine at sabot-durand.net> wrote:
> This very topic has been discussed with Ed Burns (Servlet Spec lead) and he agreed to work on moving these feature from CDI to his spec. Ideally CDI shouldn’t have dependency to front specs (servlet, jsf, jax-rs). We’ll try to work in that direction for version 2.0.

That's great to hear really. I brought the subject up at the servlet
mailing list (see
https://java.net/projects/servlet-spec/lists/users/archive/2014-11/message/11)
but there wasn't a follow up there about that discussion.

There's btw also a producer for the UserPrincipal, which I think
should ideally go to either the new security spec (again if/when it
happens) or JASPIC, and a producer for a JTA UserTransaction, which I
guess would be best off just being in JTA.

Kind regards,
Arjan






>
> Antoine
>
>
>> Le 17 nov. 2014 à 22:23, arjan tijms <arjan.tijms at gmail.com> a écrit :
>>
>> Hi,
>>
>> On Mon, Nov 17, 2014 at 10:04 PM, Antonio Goncalves
>> <antonio.goncalves at gmail.com> wrote:
>>> Like @dblevins once said "EJB was a super hype spec with all the cool
>>> features... and became blotted throughout the years". If we are not careful,
>>> CDI (the super hype spec at the moment) will become blotted too
>>
>> I strongly support that!
>>
>> IMHO as little as possible of these higher level features should be
>> implemented within CDI itself, so that CDI itself can completely focus
>> on being the contextual DI spec on which all other specs can build.
>>
>> I think it's already problematic that CDI 1.1 provided producers for
>> Servlet artifacts, instead of letting the Servlet spec itself define
>> those producers. If/when Servlet starts depending on CDI there will be
>> a rather awkward circular dependency.
>>
>> Kind regards,
>> Arjan
>> _______________________________________________
>> 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.
>