[cdi-dev] EDR1, proposed draft

[Antoine Sabot-Durand]

and if you want to only focus on async event PR 250 has also been updated, but there won’t be modification linked to contexts and observer invocation context in it. Quite hard to live with API split PR and others ;.

Antoine


> Le 23 juin 2015 à 12:07, Antoine Sabot-Durand <antoine at sabot-durand.net> a écrit :
> 
> Yes, you’ll get everything is PR 251 that I rebased to have all the modifications at hand:
> 
> https://github.com/cdi-spec/cdi/pull/251
> 
> 
>> Le 23 juin 2015 à 12:03, Jozef Hartinger <jharting at redhat.com> a écrit :
>> 
>> On 06/23/2015 11:36 AM, Antoine Sabot-Durand wrote:
>>> Last changes concerns Request and Application context in SE which should be temporarily specified for EDR1 (CDI-530 will bring the true spec to them):
>>> https://dl.dropboxusercontent.com/u/2898173/cdi-spec.html#request_context_se
>> Is there a diff/pull request anywhere on github?
>>> 
>>> They are both active during all method invocation and are destroyed when container is shut down. The difference is that application context is hared between all methods invocation
>> 
>> So request context isn't shared between method invocations? I really cannot tell from the proposal as the wording is very vague. Has any thought been given on how this is supposed to be implemented?
>> 
>> 
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: Message signed with OpenPGP using GPGMail
Url : http://lists.jboss.org/pipermail/cdi-dev/attachments/20150623/c199c3a6/attachment.bin