JBoss.orgCommunity Documentation

Chapter 1. Introduction to the CDI Telco Framework

CDI is the Java standard for dependency injection and contextual lifecycle management, led by Gavin King for Red Hat, Inc. and is a Java Community Process(JCP) specification that integrates cleanly with the Java EE platform. Any Java EE 6-compliant application server provides support for JSR-299 (even the web profile). It seemed a natural fit create a new framework based on CDI for the Telco world.

CDI-Telco-Framework (CTF) from Mobicents brings the power and productivity benefits of CDI into the Mobicents Sip Servlets platform providing dependency injection and contextual lifecycle management for converged HTTP/SIP applications. This new framework is intended to become a replacement for our previous Seam Telco Framework.

CTF mission statement is to simplify SipServlets development by introducing a component based programming model, ease of development by making available SIP utilities out of the box, and finally providing dependency injection and contextual lifecycle management to the SipServlets.

The framework is based on CDI and will stand as an extension to the core.

Figure 1.1. The framework is based on CDI and will stand as an extension to the core.


Container Support

CTF supports Mobicents Sip Servlets 1.x (JBoss AS5 - Tomcat 6.x) and Mobicents Sip Servlets 2.x (Tomcat 7.x).

Note

Support for JBoss AS5 is the same as in the Servlet environment (no EJB support, no transactions etc).

CTF consists of

CDI Telco Framework Parts

  • The first part is responsible to CDI-enable a converged application.

  • The second part is responsible to make available the SipFactory, SipSessionsUtils, TimerService and also to propage Sip requests and responses to applications.