[
https://issues.apache.org/jira/browse/OWB-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16884736#comment-16884736
]
Romain Manni-Bucau commented on OWB-1293:
-----------------------------------------
Option a has the same drawback, servlet already rejected cdi - scopes and
integration - whereas at ee level it would have been natural. So a is a promise
whereas b is already real. This is why i favor b. Now if you make a passing for
jetty and tomcat, i would be happy to join you there, just not what the reality
is today from my window.
Also note that cdi.current is portable and how integration can be maintained in
all container and integrations enable to be compatible with containers which is
not doable at servlet level (tomcat valves, ordering, advanced async support
etc).
> Update Jetty integration prior to Jetty-10 release
> --------------------------------------------------
>
> Key: OWB-1293
> URL: https://issues.apache.org/jira/browse/OWB-1293
> Project: OpenWebBeans
> Issue Type: Improvement
> Components: Interceptor and Decorators
> Reporter: Greg Wilkins
> Priority: Major
>
> The current jetty integration relies on exposing private jetty APIs so a
> jetty Decorator can be registered. This is fragile and requires different
> APIs for the upcoming jetty-10 release.
> Instead, Jetty is developing a mechanism where a object with a decorator
> signature can be set as a context attribute and it will be introspected and
> dynamically registered as a decorator without any API dependencies.
> This is currently being developed in
> [https://github.com/eclipse/jetty.project/pull/3838] and an integration with
> Weld is at [https://github.com/weld/core/pull/1926]
> Feedback is sought from the OpenWebBeans team on the approach and then we'd
> like to collaborate to make a similar integration.
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
