[
https://issues.apache.org/jira/browse/OWB-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16882029#comment-16882029
]
Greg Wilkins commented on OWB-1293:
-----------------------------------
Currently Jetty avoid providing CDI at the container level. It can be setup by
individual users, but it is not something we offer as a module. We want to be
able to run both Weld and OWB webapps in the same server, potentially at
different levels of the specification. So the model that we wish to directly
support is to have CDI within the WEB-INF/lib.
I'm trying now to make this work with a Decorator that uses reflection.... but
I'm having significant trouble as it is a complex and fragile process to do so.
Far more complex/fragile that the simple decorator set as attribute approach
that I originally proposed. I'll stick with it for a bit... but starting to
have second thoughts.
> 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.3#76005)
