Java Reference
In-Depth Information
ing Directory Index ( JNDI ) and can be looked up by both local clients and remote
clients, provided they supply the correct environment parameters. Since a connec-
tion factory can be reused multiple times in your code, it's the kind of object that can
be conveniently cached by a remote client or a message-driven bean.
The definition of connection-factory instances is included in the full and full-ha
server configurations. You can inspect them in the overall JMS configuration, which
is available by surfing the admin console and navigating to Profile | Messaging Pro-
vider :
As you can see in the preceding screenshot, there are two out-of-the-box connection
factory definitions:
InVmConnectionFactory : This connection factory is bound under the
entry java:/ConnectionFactory , and is used when the server and
client are part of the same process (that is, they are running on the same
JVM).
RemoteConnectionFactory : This connection factory, as the name im-
plies, can be used when JMS connections are provided by a remote serv-
er, using Netty as the connector.
If you want to change the connection factory's JNDI binding, the simplest choice is to
go through the server configuration file (for example, standalone-full.xml for
standalone mode):
Search WWH ::




Custom Search