Home >> All >> org >> activemq >> [ jndi Javadoc ]

• org.activemq.jndi: Javadoc index of package org.activemq.jndi.


Package Samples:

• org.activemq.jndi

Classes:

• ReadOnlyContext: A read-only Context This version assumes it and all its subcontext are read-only and any attempt to modify (e.g. through bind) will result in an OperationNotSupportedException. Each Context in the tree builds a cache of the entries in all sub-contexts to optimise the performance of lookup. This implementation is intended to optimise the performance of lookup(String) to about the level of a HashMap get. It has been observed that the scheme resolution phase performed by the JVM takes considerably longer, so for optimum performance lookups should be coded like: Context componentContext = (Context)new ...
• ActiveMQWASInitialContextFactory: This implementation of InitialContextFactory should be used when ActiveMQ is used as WebSphere Generic JMS Provider. It is proved that it works on WebSphere 5.1. The reason for using this class is that custom property defined for Generic JMS Provider are passed to InitialContextFactory only if it begins with java.naming or javax.naming prefix. Additionaly provider url for the JMS provider can not contain ',' character that is necessary when the list of nodes is provided. So the role of this class is to transform properties before passing it to ActiveMQInitialContextFactory .
• ActiveMQInitialContextFactory: A factory of the ActiveMQ InitialContext which contains javax.jms.ConnectionFactory instances as well as a child context called destinations which contain all of the current active destinations, in child context depending on the QoS such as transient or durable and queue or topic.
• JNDIReferenceFactory: Converts objects implementing JNDIStorable into a property fields so they can be stored and regenerated from JNDI
• NameParserImpl: A default implementation of javax.naming.NameParser
• AdminObjectTest: Test that the admin objects can be stored and looked up in JNDI providers.
• JNDIBaseStorable: Faciliates objects to be stored in JNDI as properties
• JNDIStorableInterface: Faciliates objects to be stored in JNDI as properties
• LazyCreateContext: Allows users to dynamically create items
• CustomConnectionFactoryNameTest: Test case for AMQ-141
• DestinationNameWithSlashTest: Test case for AMQ-140
• ActiveMQInitialContextFactoryTest
• InitialContextTest
• JNDITestSupport

Home | Contact Us | Privacy Policy | Terms of Service