Java Reference
In-Depth Information
«
interface
»
Connection
Connector
opens
opens
0..1
«
interface
»
SipErrorListener
«
interface
»
SipConnection
«
interface
»
SipConnectionNotifier
1
1
«
interface
»
SipDialog
0..1
1
«
interface
»
SipServer
ConnectionListener
*
1
*
*
1
*
«
interface
»
SipClientConnection
«
interface
»
SipServerConnection
SipRefresh
Helper
SipAddress
1
0..*
1
0..1
«
interface
»
SipClient
ConnectionListener
«
exception
»
SipException
«
interface
»
SipRefreshListener
SipHeader
javax.microedition.sip
core interface
exception class
CLDC class
helper class/interface
Figure 11.7
JSR-180 SIP classes
SIP messages in and out of SIP dialogs. Figure 11.7 illustrates the relations
between JSR-180 API classes and interfaces.
IntegrationwithNativeServices
The native Symbian OS SIP architecture is too elaborate to fully explain
in the context and within the scope of this chapter. The native SIP service
contains a very large number of classes, with an architecture which
is considerably more complex than the generic and compact Java ME
architecture; it is decomposed into more than one set of APIs. This is
only one of the differences that make the integration of JSR-180 SIP very
challenging.
The native and Java APIs are very different from one another so the
two are difficult to compare. We consider a number of the differences
between the Java and native architectures that indicate how different they
are and see how the two APIs can be bound.
JSR-180 SIP was designed to be a compact and generic API, in
regard to the SIP methods and headers, and the designer chose to use
