As well as writing pure SIP Servlet applications, developers can use Rhino SIP Servlet to write hybrid applications: SLEE services that use the SIP Servlet RA Type API.
This means they can make use of the nice features in the SIP Servlet API (such as built-in proxying), while also using the SLEE component model (SBBs, events, activities, activity contexts, and so on).
Participating in application selection
Hybrid applications can take part in the application-selection process, controlled by the Application Router. SIP Servlet and hybrid applications can be composed together on the same SIP call.
Hybrid applications are normal SLEE services, so are identified by their ServiceID. The Application Router uses application names to refer to the applications it selects. When deploying a hybrid application, the deployer must also manually create an application name so that the Application Router can select it.
Hybrid application example
The examples/proxy-hybrid directory in the Rhino SIP Servlet package contains an example SLEE service that uses the SIP Servlet API to implement a simple proxy.
Run “ant deploy” in the examples/proxy-hybrid directory to deploy the service.
Note that the service does not perform any SIP registration lookups; it simply forwards requests to the next hop.
