Connection object is a client's active connection to its JMS provider.
More...
#include <javax_jms_Connection.h>
Inheritance diagram for javax::jms::Connection:


Public Types | |
| enum | { xmogDefaultFlags = xmog_base::GLOBAL, xmogMajorVersion = 3, xmogMinorVersion = 2, xmogPatchVersion = 9, xmogBuildNumber = 2047 } |
|
typedef ::xmog_java_array_template< ::javax::jms::Connection > | array1D |
|
typedef ::xmog_java_array_template< ::xmog_java_array_template< ::javax::jms::Connection > > | array2D |
Public Member Functions | |
| virtual void | close (::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
| Closes the connection. | |
| virtual ::javax::jms::ConnectionConsumer | createConnectionConsumer (const ::javax::jms::Destination &destination, const ::java::lang::String &messageSelector, const ::javax::jms::ServerSessionPool &sessionPool, jint maxMessages,::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
| Creates a connection consumer for this connection (optional operation). | |
| virtual ::javax::jms::ConnectionConsumer | createDurableConnectionConsumer (const ::javax::jms::Topic &topic, const ::java::lang::String &subscriptionName, const ::java::lang::String &messageSelector, const ::javax::jms::ServerSessionPool &sessionPool, jint maxMessages,::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
| Create a durable connection consumer for this connection (optional operation). | |
| virtual ::javax::jms::Session | createSession (bool transacted, jint acknowledgeMode,::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
Creates a Session object. | |
| virtual ::java::lang::String | getClientID (::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
| Gets the client identifier for this connection. | |
| virtual ::javax::jms::ExceptionListener | getExceptionListener (::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
Gets the ExceptionListener object for this connection. | |
| virtual ::javax::jms::ConnectionMetaData | getMetaData (::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
| Gets the metadata for this connection. | |
| virtual void | setClientID (const ::java::lang::String &clientID,::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
| Sets the client identifier for this connection. | |
| virtual void | setExceptionListener (const ::javax::jms::ExceptionListener &listener,::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
| Sets an exception listener for this connection. | |
| virtual void | start (::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
| Starts (or restarts) a connection's delivery of incoming messages. | |
| virtual void | stop (::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
| Temporarily stops a connection's delivery of incoming messages. | |
Connection object is a client's active connection to its JMS provider.
It typically allocates provider resources outside the Java virtual machine (JVM).
Connections support concurrent use.
A connection serves several purposes:
ConnectionMetaData object. ExceptionListener object. Because the creation of a connection involves setting up authentication and communication, a connection is a relatively heavyweight object. Most clients will do all their messaging with a single connection. Other more advanced applications may use several connections. The JMS API does not architect a reason for using multiple connections; however, there may be operational reasons for doing so.
A JMS client typically creates a connection, one or more sessions, and a number of message producers and consumers. When a connection is created, it is in stopped mode. That means that no messages are being delivered.
It is typical to leave the connection in stopped mode until setup is complete (that is, until all message consumers have been created). At that point, the client calls the connection's start method, and messages begin arriving at the connection's consumers. This setup convention minimizes any client confusion that may result from asynchronous message delivery while the client is still in the process of setting itself up.
A connection can be started immediately, and the setup can be done afterwards. Clients that do this must be prepared to handle asynchronous message delivery while they are still in the process of setting up.
A message producer can send messages while a connection is stopped.
Rich Burridge
Kate Stout
|
||||||||||||
|
Closes the connection. Since a provider typically allocates significant resources outside the JVM on behalf of a connection, clients should close these resources when they are not needed. Relying on garbage collection to eventually reclaim these resources may not be timely enough. There is no need to close the sessions, producers, and consumers of a closed connection. Closing a connection causes all temporary destinations to be deleted.
When this method is invoked, it should not return until message processing has been shut down in an orderly fashion. This means that all message listeners that may have been running have returned, and that all pending receives have returned. A close terminates all pending message receives on the connection's sessions' consumers. The receives may return with a message or with null, depending on whether there was a message available at the time of the close. If one or more of the connection's sessions' message listeners is processing a message at the time when connection
Closing a connection causes any of its sessions' transactions in progress to be rolled back. In the case where a session's work is coordinated by an external transaction manager, a session's Closing a connection does NOT force an acknowledgment of client-acknowledged sessions.
Invoking the
|
|
||||||||||||||||||||||||||||
|
Creates a connection consumer for this connection (optional operation). This is an expert facility not used by regular JMS clients.
|
|
||||||||||||||||||||||||||||||||
|
Create a durable connection consumer for this connection (optional operation). This is an expert facility not used by regular JMS clients.
Reimplemented in javax::jms::TopicConnection, and javax::jms::XATopicConnection. |
|
||||||||||||||||||||
|
Creates a
Reimplemented in javax::jms::XAConnection, javax::jms::XAQueueConnection, and javax::jms::XATopicConnection. |
|
||||||||||||
|
Gets the client identifier for this connection.
This value is specific to the JMS provider. It is either preconfigured by an administrator in a
|
|
||||||||||||
|
Gets the
Not every
|
|
||||||||||||
|
Gets the metadata for this connection.
|
|
||||||||||||||||
|
Sets the client identifier for this connection.
The preferred way to assign a JMS client's client identifier is for it to be configured in a client-specific
Alternatively, a client can set a connection's client identifier using a provider-specific value. The facility to set a connection's client identifier explicitly is not a mechanism for overriding the identifier that has been administratively configured. It is provided for the case where no administratively specified identifier exists. If one does exist, an attempt to change it by setting it must throw an The purpose of the client identifier is to associate a connection and its objects with a state maintained on behalf of the client by a provider. The only such state identified by the JMS API is that required to support durable subscriptions.
If another connection with the same
|
|
||||||||||||||||
|
Sets an exception listener for this connection.
If a JMS provider detects a serious problem with a connection, it informs the connection's An exception listener allows a client to be notified of a problem asynchronously. Some connections only consume messages, so they would have no other way to learn their connection has failed.
A connection serializes execution of its A JMS provider should attempt to resolve connection problems itself before it notifies the client of them.
|
|
||||||||||||
|
Starts (or restarts) a connection's delivery of incoming messages.
A call to
|
|
||||||||||||
|
Temporarily stops a connection's delivery of incoming messages.
Delivery can be restarted using the connection's This call blocks until receives and/or message listeners in progress have completed.
Stopping a connection has no effect on its ability to send messages. A call to
A call to
If message listeners are running when
|
1.4.1