📄 package-summary.html
字号:
<P>
<TABLE BORDER="1" WIDTH="100%" CELLPADDING="3" CELLSPACING="0" SUMMARY="">
<TR BGCOLOR="#CCCCFF" CLASS="TableHeadingColor">
<TH ALIGN="left" COLSPAN="2"><FONT SIZE="+2">
<B>Exception Summary</B></FONT></TH>
</TR>
<TR BGCOLOR="white" CLASS="TableRowColor">
<TD WIDTH="15%"><B><A HREF="../../javax/sip/DialogDoesNotExistException.html" title="class in javax.sip">DialogDoesNotExistException</A></B></TD>
<TD>This Exception is thrown when a user attempts to reference Dialog that does currently not exist in the underlying SipProvider</TD>
</TR>
<TR BGCOLOR="white" CLASS="TableRowColor">
<TD WIDTH="15%"><B><A HREF="../../javax/sip/InvalidArgumentException.html" title="class in javax.sip">InvalidArgumentException</A></B></TD>
<TD>This exception class is thrown by an implementation when given an invalid argument such as a invalid numerical value.</TD>
</TR>
<TR BGCOLOR="white" CLASS="TableRowColor">
<TD WIDTH="15%"><B><A HREF="../../javax/sip/ObjectInUseException.html" title="class in javax.sip">ObjectInUseException</A></B></TD>
<TD>This exception is thrown by a method that is unable to delete a specified Object because the Object is still in use by the underlying implementation.</TD>
</TR>
<TR BGCOLOR="white" CLASS="TableRowColor">
<TD WIDTH="15%"><B><A HREF="../../javax/sip/PeerUnavailableException.html" title="class in javax.sip">PeerUnavailableException</A></B></TD>
<TD>The PeerUnavailableException indicates that a vendor's implementation of a JAIN SIP interface could not be created for some reason.</TD>
</TR>
<TR BGCOLOR="white" CLASS="TableRowColor">
<TD WIDTH="15%"><B><A HREF="../../javax/sip/ProviderDoesNotExistException.html" title="class in javax.sip">ProviderDoesNotExistException</A></B></TD>
<TD>This Exception is thrown when a user attempts to start the SipStack without any SipProviders created to service requests and responses.</TD>
</TR>
<TR BGCOLOR="white" CLASS="TableRowColor">
<TD WIDTH="15%"><B><A HREF="../../javax/sip/SipException.html" title="class in javax.sip">SipException</A></B></TD>
<TD>A SipException is thrown when a general SIP exception is encountered, when no other specialized exception defined in this specification can handle the error.</TD>
</TR>
<TR BGCOLOR="white" CLASS="TableRowColor">
<TD WIDTH="15%"><B><A HREF="../../javax/sip/TransactionAlreadyExistsException.html" title="class in javax.sip">TransactionAlreadyExistsException</A></B></TD>
<TD>This Exception is thrown when a user attempts to get a transaction to handle a message when infact a transaction is already handling this message.</TD>
</TR>
<TR BGCOLOR="white" CLASS="TableRowColor">
<TD WIDTH="15%"><B><A HREF="../../javax/sip/TransactionDoesNotExistException.html" title="class in javax.sip">TransactionDoesNotExistException</A></B></TD>
<TD>This Exception is thrown when a user attempts to reference a client or server transaction that does currently not exist in the underlying SipProvider</TD>
</TR>
<TR BGCOLOR="white" CLASS="TableRowColor">
<TD WIDTH="15%"><B><A HREF="../../javax/sip/TransactionUnavailableException.html" title="class in javax.sip">TransactionUnavailableException</A></B></TD>
<TD>The TransactionUnavailableException indicates that a vendor's implementation could not create a Transaction for some reason.</TD>
</TR>
<TR BGCOLOR="white" CLASS="TableRowColor">
<TD WIDTH="15%"><B><A HREF="../../javax/sip/TransportAlreadySupportedException.html" title="class in javax.sip">TransportAlreadySupportedException</A></B></TD>
<TD>The TransportAlreadySupportedException indicates that a specific transport is already supported by a SipProvider via its ListeningPoints.</TD>
</TR>
<TR BGCOLOR="white" CLASS="TableRowColor">
<TD WIDTH="15%"><B><A HREF="../../javax/sip/TransportNotSupportedException.html" title="class in javax.sip">TransportNotSupportedException</A></B></TD>
<TD>The TransportNotSupportedException indicates that a specific transport is not supported by a vendor's implementation of this specification.</TD>
</TR>
</TABLE>
<P>
<A NAME="package_description"><!-- --></A><H2>
Package javax.sip Description
</H2>
<P>
<p> This package contains the main interfaces that model the architecture
from both an application developer and a stack vendor view.</p>
<ul>
<li>Application Developer View:<br>
The application developer is concerned with implementing the
<it> SipListener </it> interface. This Interface defines the methods required by applications
to receive and process messages from a vendors SIP stack.
<href ="SipEvent.html">
A SipProvider receives messages from the underlying SIP
network, which in turn encapsulates these messages as Events and passes
them to its registered SipListener.</href>
An application must register with
a SipProvider to listen for Events by implementing the
SipListener interface.
A single SipListener interface is mandated in the architecture.<br>
<br>
</li>
<li>Stack Vendors View:<br>
The stack vendor implements all the interfaces in this specification
excluding the SipListener interface,
however the two most important interfaces
from the architecture point of view are the <a href="SipStack.html">SipStack</a>
and the <a href="SipProvider.html">SipProvider</a> interfaces.<br></li>
<ul>
<li>
<p>SipStack - This interface can be viewed as the stack management interface
of the architecture. The SipStack interface encapsulates the dynamic
management characteristics
of the SIP stack, such as ListeningPoints which encapsulate port
and transport. As well as the central
point for the creation and querying of SipProviders in the architecture
. </p>
</li>
<li>
<p>SipProvider - This interface can be viewed as the messaging
interface of the architecture. Multiple SipProviders are allowed
within the architecture. This interface defines the methods that allow
an application implementing the SipListener to register with the SipProvider
to recieve incoming requests and responses. The methods defined to
send SIP messages are also defined within the SipProvider<href
="message/Message.html"> interface. </href><br>
</p>
</li>
</ul>
</ul>
<b>Messaging model:</b><br>
The architecture specifies that outgoing messages are sent via the
SipProvider and can either be of type <a href="message/Request.html">Request
</a>or <a href="message/Response.html">Response</a>. This action is initiated
by the application. Incoming messages
on the other hand are passed to an application registered to the SipProvider
and can either be of type <a href="RequestEvent.html">RequestEvent </a>or
<a href="ResponseEvent.html">ResponseEvent</a>, each containing a Request
or Response message respectively. This architecture follows the Listener/Provider event
model, which is suitable for applications that are unsure when the next event
will arrive i.e. the applications listens for it. <br>
<br>
<P>
<P>
<DL>
</DL>
<HR>
<!-- ======= START OF BOTTOM NAVBAR ====== -->
<A NAME="navbar_bottom"><!-- --></A>
<A HREF="#skip-navbar_bottom" title="Skip navigation links"></A>
<TABLE BORDER="0" WIDTH="100%" CELLPADDING="1" CELLSPACING="0" SUMMARY="">
<TR>
<TD COLSPAN=2 BGCOLOR="#EEEEFF" CLASS="NavBarCell1">
<A NAME="navbar_bottom_firstrow"><!-- --></A>
<TABLE BORDER="0" CELLPADDING="0" CELLSPACING="3" SUMMARY="">
<TR ALIGN="center" VALIGN="top">
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="../../overview-summary.html"><FONT CLASS="NavBarFont1"><B>Overview</B></FONT></A> </TD>
<TD BGCOLOR="#FFFFFF" CLASS="NavBarCell1Rev"> <FONT CLASS="NavBarFont1Rev"><B>Package</B></FONT> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <FONT CLASS="NavBarFont1">Class</FONT> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="package-tree.html"><FONT CLASS="NavBarFont1"><B>Tree</B></FONT></A> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="../../deprecated-list.html"><FONT CLASS="NavBarFont1"><B>Deprecated</B></FONT></A> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="../../index-all.html"><FONT CLASS="NavBarFont1"><B>Index</B></FONT></A> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="../../help-doc.html"><FONT CLASS="NavBarFont1"><B>Help</B></FONT></A> </TD>
</TR>
</TABLE>
</TD>
<TD ALIGN="right" VALIGN="top" ROWSPAN=3><EM>
<b>JSIP API v1.2<br><font size=-1>November 2006</font></b></EM>
</TD>
</TR>
<TR>
<TD BGCOLOR="white" CLASS="NavBarCell2"><FONT SIZE="-2">
PREV PACKAGE
<A HREF="../../javax/sip/address/package-summary.html"><B>NEXT PACKAGE</B></A></FONT></TD>
<TD BGCOLOR="white" CLASS="NavBarCell2"><FONT SIZE="-2">
<A HREF="../../index.html?javax/sip/package-summary.html" target="_top"><B>FRAMES</B></A>
<A HREF="package-summary.html" target="_top"><B>NO FRAMES</B></A>
<SCRIPT type="text/javascript">
<!--
if(window==top) {
document.writeln('<A HREF="../../allclasses-noframe.html"><B>All Classes</B></A>');
}
//-->
</SCRIPT>
<NOSCRIPT>
<A HREF="../../allclasses-noframe.html"><B>All Classes</B></A>
</NOSCRIPT>
</FONT></TD>
</TR>
</TABLE>
<A NAME="skip-navbar_bottom"></A>
<!-- ======== END OF BOTTOM NAVBAR ======= -->
<HR>
<center>If you have any comments, please mail them to <a href=mailto:JAIN-SIP-INTEREST@java.sun.com>JAIN-SIP-INTEREST@java.sun.com</a> after subscribing at <a href=http://archives.java.sun.com>http://archives.java.sun.com</a><br><a href=../../copyright.html>Copyright</a> - 2006 BEA Systems and Sun Microsystems</center>
</BODY>
</HTML>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -