The Resin 4 core and configuration is built around the Java EE standard CDI dependency injection. Every Resin configuration from the resin.xml to resin-web.xml uses CDI as its configuration engine. CanDI is Resin’s implementation of Java CDI and it is core to Resin 4 Java Application Server.

With CanDI, your own applications can be clearly structured for testing, development, and maintenance as encouraged by the clean design CDI encourages.

The CDI community-designed extensions have become a key shared resource for Java developers, reusing design patterns created by other developers solving the same problems.

The custom, typesafe binding annotations are key to CDI’s self-documentation, because injection points clearly describe the resources or services they expect with adjective-oriented annotations. The annotations are true Java classes; they are documented in JavaDoc and verified by the compiler. Because the binding annotations are a small number of meaningful adjectives, they don’t impose a significant coding burden, and are well worth the small extra development time.

• standard: JavaEE Web Profile standard ensures compatibility between implementations, frameworks, applications, and IDEs.
• compact: the standards process keeps CDI well-defined, complete and compact.
• safe: compiler type-safe checking validates code correctness.
• clean: annotation processing keeps code focused and configuration tidy.
• flexible: minimal XML focuses on needed configuration, leaving boilerplate connections for auto-injection.
• powerful: interceptors, decorators and a typed event system fill out a complete feature set.
• extensible: standard extension framework gives library developers the space to experiment with features.