[
https://issues.apache.org/jira/browse/OWB-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885913#comment-16885913
]
Greg Wilkins commented on OWB-1293:
-----------------------------------
My proposal for option A does not require servlets to be extended specifically
for CDI. It requires that servlets provide a generic decorate/inject
mechanism. I am the current co-spec lead of the servlet-specification and I
am very interested in getting a portable solution. Option a) is something I
can bring to the spec process, option b) is not.
Also, the reality I see is that I've not been able to get option B to work with
OWBs, the same code that works with Weld, does not work with OWBs (see above),
so the portability of that approach is not apparent to me. It will also be
reliant of ordering of SCI, which is currently not a standard feature of
servlets. Finally, it also indicates that getting Jetty to debug/maintain the
CDI integrations is not a good idea as we don't really have the experience and
simply don't want to become experts in every CDI implementation. The problem
is almost certainly something silly that I've done, but I don't know, I'm not
an CDI expert. I call inject, it works for Weld, fails for OWB, ????
If Weld and OWB want option B (or C or D for that matter), then Jetty would do
that. But currently I have Weld and OWB wanting 2 different approaches, so I
have to pick one and at the moment that will be option A for the reasons I list
above. So if you want option B, then it is not me that you have to convince,
but the Weld guys - so talk to them in [https://github.com/weld/core/pull/1926]
B could definitely work, but only if all parties push for it.
> 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)
