[cdi-dev] prd review

[Pete Muir]

On 3 Nov 2012, at 14:37, Pete Muir wrote:

> 
> On 3 Nov 2012, at 07:40, Mark Struberg wrote:
> 
>> Hi folks!
>> 
>> I think there are still a few paragraphs in there which I personally thought we already dropped again
>> 
>> I gonna review the spec page by page the next 2 weeks.
>> 
>> in 'Foreward' (btw shouldn't that be 'Foreword'?)
> 
> Ooops ;-) Please file a JIRA.

This is correct in the version I downloaded from jcp.org...


> 
>> 
>> * "Ability to veto beans declaratively using @Veto and @Requires"
>> I thought we dropped @Requires as it's not really possible to implement that properly? That would require any scanning mechanism to know CDI and it's mechanics.
>> At least this references to a valid paragraph ;) -> should get fixed too.
>> 
>> 
>> * "Ability to access the BeanManager from the ServletContext"
>> Didn't we drop that as well? I wasnt able to find the definition in the rest of the spec.
> 
> Both of these I missed removing from the 1.0 -> EDR list. Again, JIRA it.
> 
>> 
>> * "Ability to obtain Extension instances from BeanManager" 
>> As above, do we really have this now? Thought we dont need it as its perfectly possible to @Inject Extensions since CDI-1.0
> 
> This is still in. Please file a JIRA.
> 
>> 
>> 
>> Foreword misses a reference to CDI-18 which is imo the most important change.
> 
> This is there - 	• Global ordering and enablement of interceptors and decorators
> 
> 	• Global selection of alternatives
> 
>> 
>> 
>> 
>> 
>> Just for the start :)
>> 
>> LieGrue,
>> strub
>> 
>> 
>> _______________________________________________
>> cdi-dev mailing list
>> cdi-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/cdi-dev
> 
> 
> _______________________________________________
> cdi-dev mailing list
> cdi-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/cdi-dev