That is a webapp used to experiment with container initialized CDI. Container Initialized CDI is an experimental feature of Jetty 9.3, one we are trying to wrap our heads around. The idea of Container Initialized CDI is one that is making noise with the upcoming JEE8 / Servlet 4 specs.
Currently, the --module=cdi configuration on Jetty 9.3 distribution will enable container initialized CDI for all webapps deployed on that server instance. Now, as for the more important question ... why are you asking tomcat and jersey questions on an Eclipse Jetty mailing list? -- Joakim Erdfelt <[email protected]> webtide.com <http://www.webtide.com/> - intalio.com/jetty Expert advice, services and support from from the Jetty & CometD experts eclipse.org/jetty - cometd.org On Mon, May 4, 2015 at 10:16 PM, jason zhang <[email protected]> wrote: > I compiled this example project. I used the tomcat-packaging profile. The > generated war file does not have anything as is document in weld > documentation( > http://docs.jboss.org/weld/reference/latest-2.2/en-US/html/environments.html#_tomcat > ). > > How is weld boostrapped? Is it bootstrapped by jersey? > > Thanks > > -- > -jiesheng > > _______________________________________________ > jetty-users mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/jetty-users >
_______________________________________________ jetty-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jetty-users
