[
https://issues.apache.org/jira/browse/OWB-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16894307#comment-16894307
]
Romain Manni-Bucau commented on OWB-1293:
-----------------------------------------
[[email protected]]
[https://github.com/apache/openwebbeans/blob/master/webbeans-jetty9/src/main/java/org/apache/webbeans/web/jetty9/JettyDecorator.java]
does the tracking, so you have a key ;). destroy is mainly @PreDestroy so must
be call before context.release(). You can use Unmanaged
([https://github.com/agoncal/cdi-spec/blob/master/api/src/main/java/javax/enterprise/inject/spi/Unmanaged.java])
to have the correct lifecycle. Just skip postconstruct/predestroy since jetty
should already handle it, right? To answer the CDI spi point you mention: I
agree but this is likely not the integration API, injectiontarget is likely
better (or unmanaged abstraction).
Hope it helps.
> 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)
