[ 
https://issues.apache.org/jira/browse/OWB-1451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18021840#comment-18021840
 ] 

Thomas Andraschko commented on OWB-1451:
----------------------------------------

If there are no objections, i would start a 4.1 branch and begin with stuff 
like 6)

It would be great if romain or mark can help a bit in the more heavier tasks, i 
dont know the internals that good.

> CDI 4.1
> -------
>
>                 Key: OWB-1451
>                 URL: https://issues.apache.org/jira/browse/OWB-1451
>             Project: OpenWebBeans
>          Issue Type: New Feature
>            Reporter: Thomas Andraschko
>            Priority: Major
>
> https://jakarta.ee/specifications/cdi/4.1/jakarta-cdi-spec-4.1#_jakarta_contexts_and_dependency_injection_4_1
> 1) CDI 4.1 no longer specifies integration with Jakarta EE. This will now be 
> specified in the Jakarta EE Platform, Web Profile and Core Profile 
> specifications.
> 2) The Unified EL integration API in BeanManager has been deprecated and the 
> relevant methods added to a dedicated interface ELAwareBeanManager, which is 
> present in a new supplemental API artifact: 
> jakarta.enterprise:jakarta.enterprise.cdi-el-api. This supplemental artifact 
> declares a JPMS module jakarta.cdi.el, which declares a dependency on 
> jakarta.cdi and jakarta.el.
> 3) The method invokers API has been added to allow frameworks to more easily 
> call methods on managed beans and optionally look up the bean instance and 
> arguments using CDI.
> 4) New methods have been added to BeanContainer to check assignability of 
> beans and events and to obtain contexts for a scope.
> 5) The @Priority annotation can now be placed on producer methods and 
> producer fields directly.
> 6) A new beans.xml 4.1 schema file has been added and the namespace of the 
> beans_4_1.xsd schema file is 
> xmlns:jakartaee="https://jakarta.ee/xml/ns/jakartaee";. The only change in the 
> schema is to update the default value for the version to 4.1 and update the 
> example to use the new version.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to