The classpath should include weld servlet

Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Explaining the semiconductor shortage, and how it might end. Does ES6 make JavaScript frameworks obsolete? Featured on Meta. Now live: A fully responsive profile. Related Hot Network Questions. Question feed. Stack Overflow works best with JavaScript enabled. There is a common pattern for all above mentioned containers.

In other words, in all above cases, Jersey application must be deployed as a Servlet, where the underlying Servlet container has CDI integrated already and CDI container bootstrapped properly. If this feature was missing, you would not be able to use any request scoped CDI beans in your Jersey application. To make Jersey work with CDI in containers that do not have request scope binding resolved, some extra work is required.

For performance reasons, at most a single external request scope provider is allowed by Jersey runtime. Example Bootstrapping Jersey application with Weld support on Grizzly. You simply add the above mentioned jersey-weld2-se module into you class-path and bootstrap the Weld container manually before starting the HTTP container. In addition to improved integration of the Enterprise Java stack, the "Contexts and Dependency Injection for the Java EE platform" specification also defines a state of the art typesafe, stateful dependency injection framework, which can prove useful in a wide range of application types.

Managed beans with PostConstruct and PreDestroy lifecycle callbacks. Application , Dependent and Singleton scopes. Weld provides an extension which will boot a CDI bean manager in Java SE, automatically registering all simple beans found on the classpath.

The command line parameters can be injected using either of the following:. The command line parameters do not become available for injection until the ContainerInitialized event is fired. If you need access to the parameters during initialization you can do so via the public static String[] getParameters method in StartMain. Thanks to the power of CDI's typesafe event model, application developers need not write any bootstrapping code.

The entry point for your application code would therefore be a simple bean which observes the ContainerInitialized event, as in the previous example. In this case your application can be started by calling the provided main method like so:.

Alternatively the application could be started by firing a custom event which would then be observed by another simple bean. The following example fires MyEvent on startup. In contrast to Java EE applications, Java SE applications place no restrictions on developers regarding the creation and usage of threads.

Therefore Weld SE provides a custom scope annotation, ThreadScoped , and corresponding context implementation which can be used to bind bean instances to the current thread. It is intended to be used in scenarios where you might otherwise use ThreadLocal , and does in fact use ThreadLocal under the hood. To use the ThreadScoped annotation you need to enable the RunnableDecorator which 'listens' for all executions of Runnable. It is not necessary to use ThreadScoped in all multithreaded applications.

The thread context is not intended as a replacement for defining your own application-specific contexts. It is generally only useful in situations where you would otherwise have used ThreadLocal directly, which are typically rare.