A JBoss Project
Red Hat
CDI tagcloud

Weld is the reference implementation of CDI: Contexts and Dependency Injection for the Java EE Platform which is the Java standard for dependency injection and contextual lifecycle management and one of the most important and popular parts of the Java EE platform.

Weld is integrated into many Java EE application servers such as WildFly, JBoss Enterprise Application Platform, GlassFish, Oracle WebLogic and others. Weld can also be used in a Servlet-only environment (Tomcat, Jetty) or plain Java SE environment.

Try Weld Today

To use Weld today, download the WildFly server (formelly JBoss AS) and add the following code to the pom.xml file of your application:

<dependency>
   <groupId>javax.enterprise</groupId>
   <artifactId>cdi-api</artifactId>
   <version>1.1</version>
   <scope>provided</scope>
</dependency>

For alternative ways of using Weld, see the download section or the reference documentation.

Weld Book

The latest book on Weld is now available:

News

  • Weld 2.2 (CDI 1.2 reference implementation) released!

    2014-4-15: Jozef Hartinger

    Today we released Weld 2.2.0.Final - the reference implementation of Contexts and Dependency Injection for Java EE 1.2 (CDI 1.2). Besides implementing the changes in the specification, this release comes with several new features, performance improvements and more than 50 bug fixes. CDI 1.2 CDI 1.2 is a maintenance release of the CDI...

    Read more »
  • CDI 1.2 and Weld 2.2

    2014-2-4: Jozef Hartinger

    Work on a maintenance release of the CDI specification (CDI 1.2) has started recently. Now is the best time to add feedback on issues being addressed. Most of the discussion happens in the cdi-dev mailing list or the IRC channel. Weld 2.2 is going to be the reference implementation of CDI...

    Read more »
  • Three new Weld releases

    2014-1-14: Jozef Hartinger

    This week we are releasing three new builds of Weld. Firstly, Weld 2.1.2.Final was released. This is a bug-fixing release with 11 issues resolved. Most notably: The conversation context is now initialized lazily. This resolves the problem with custom character encoding that many of you run into. See the reference documentation...

    Read more »