Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[jetty-dev] Jetty CDI/Weld integration and Arquillian container

Hello Jetty devs,

recently we came accross a problem while deploying a webapp with bundled Weld Servlet to a Jetty standalone instance [1]. The investigation resulted in a new FAQ entry in Weld [2] and also a Jetty bug [3]. The CDI/Weld module which is part of the Jetty dist since 9.2.4 looks good except the Jetty docs mention a wrong module name - "weld" instead of "cdi" [4].

Nevertheless, it would be great to finish the Arquillian Jetty container cleanup started by Joakim Erdfelt. Is there any open issue or should we initiate a new release (1.0.0.CR2 was released on 22 Jul 2013)? The other question is whether it would be possible to implement a managed Jetty container so that we could detect similar issues in our test suite. Weld team is ready to help. We don't have a deep knowledge of Jetty though ;-)

Thanks,

Martin (on behalf of Weld team)


[1]
https://issues.jboss.org/browse/WELD-1959

[2]
http://weld.cdi-spec.org/documentation/#11

[3]
https://bugs.eclipse.org/bugs/show_bug.cgi?id=469384

[4]
http://www.eclipse.org/jetty/documentation/current/framework-weld.html

--
Martin Kouba
Software Engineer
Red Hat, Czech Republic


Back to the top