javax.jms
Interface ConnectionFactory

All Known Subinterfaces:

QueueConnectionFactory, TopicConnectionFactory, XAQueueConnectionFactory, XATopicConnectionFactory

All Known Implementing Classes:

JMQConnectionFactory

public interface ConnectionFactory

A ConnectionFactory object encapsulates a set of connection configuration parameters that has been defined by an administrator. A client uses it to create a connection with a JMS provider.

ConnectionFactory objects support concurrent use.

A ConnectionFactory object is a JMS administered object.

JMS administered objects are objects containing configuration information that are created by an administrator and later used by JMS clients. They make it practical to administer the JMS API in the enterprise.

Although the interfaces for administered objects do not explicitly depend on the Java Naming and Directory Interface (JNDI) API, the JMS API establishes the convention that JMS clients find administered objects by looking them up in a JNDI namespace.

An administrator can place an administered object anywhere in a namespace. The JMS API does not define a naming policy.

It is expected that JMS providers will provide the tools an administrator needs to create and configure administered objects in a JNDI namespace. JMS provider implementations of administered objects should be both javax.jndi.Referenceable and java.io.Serializable so that they can be stored in all JNDI naming contexts. In addition, it is recommended that these implementations follow the JavaBeans^TM design patterns.

This strategy provides several benefits:

• It hides provider-specific details from JMS clients.
• It abstracts administrative information into objects in the Java programming language ("Java objects") that are easily organized and administered from a common management console.
• Since there will be JNDI providers for all popular naming services, this means that JMS providers can deliver one implementation of administered objects that will run everywhere.

An administered object should not hold on to any remote resources. Its lookup should not use remote resources other than those used by the JNDI API itself.

Clients should think of administered objects as local Java objects. Looking them up should not have any hidden side effects or use surprising amounts of local resources.

See Also:

QueueConnectionFactory, TopicConnectionFactory

Field Detail

value

public Binding[] value

BindingListHolder

public BindingListHolder()

BindingListHolder

public BindingListHolder(Binding[] value)

_read

public void _read(InputStream is)

Description copied from interface: Streamable

Reads data from istream and initalizes the value field of the Holder with the unmarshalled data.

Specified by:

_read in interface Streamable

Following copied from interface: org.omg.CORBA.portable.Streamable

Parameters:

istream - the InputStream that represents the CDR data from the wire.

_write

public void _write(OutputStream os)

Description copied from interface: Streamable

Marshals to ostream the value in the value field of the Holder.

Specified by:

_write in interface Streamable

Following copied from interface: org.omg.CORBA.portable.Streamable

Parameters:

ostream - the CDR OutputStream

_type

public TypeCode _type()

Description copied from interface: Streamable

Retrieves the TypeCode object corresponding to the value in the value field of the Holder.

Specified by:

_type in interface Streamable

Following copied from interface: org.omg.CORBA.portable.Streamable

Returns:

the TypeCode object for the value held in the holder