weblogic.jms.extensions

Interface RegistrationHandle

All Known Implementing Classes:

JMSDestinationAvailabilityHelper.DestinationAvailabilityListenerWrapper

public interface RegistrationHandle

The handle given back to a caller after a successful JMSDestinationAvailabilityHelper registration. A caller can then use this handle to unregister the associated DestinationAvailabilityListener and stop receiving destination availability updates.

See Also:

JMSDestinationAvailabilityHelper

Method Summary

Modifier and Type	Method and Description
javax.jms.ConnectionFactory	lookupConnectionFactory(java.lang.String jndiName)
javax.jms.Destination	lookupDestination(java.lang.String jndiName)
java.lang.Object	runAs(java.security.PrivilegedExceptionAction action)
void	unregister() Unregister the associated DestinationAvailabilityListener and stop receiving destination availability updates.

Method Detail

unregister

void unregister()

Unregister the associated DestinationAvailabilityListener and stop receiving destination availability updates.

See Also:

JMSDestinationAvailabilityHelper.register(java.util.Hashtable, java.lang.String, weblogic.jms.extensions.DestinationAvailabilityListener)

lookupConnectionFactory

javax.jms.ConnectionFactory lookupConnectionFactory(java.lang.String jndiName)
                                             throws javax.naming.NamingException

Parameters:

jndiName - The JNDIName of the JMS connection factory.

Returns:

An instance of ConnectionFactory

Throws:

java.lang.IllegalStateException - if the first onDestinationsAvailable() callback has not been called.

javax.naming.NamingException - if the lookup is not successful.

Excluded in public API Reference.

Look up the JMS connection factory using the right subject based on the JNDI properties and destination JNDI name provided in the register call.

This method should not be called before the first onDestinationsAvailable() is received by the listener of this registration.

The lookup will be done using the JNDI context that the JMSDestinationAvailabilityHelper has established with the server on behalf of the right subject. If security credentials are provided in the JNDI properties when the registration is made with the JMSDestinationAvailabilityHelper, these credentials will be used. Otherwise, the original subject that is on the application thread when the registration is made will be used unless the JMS destination is running in a different WLS domain. In the cross-domain case, the anonymous subject is used, instead of the original subject. If the listener is running on a WLS and the resultant subject is server identity, anonymous credentials will be used.

lookupDestination

javax.jms.Destination lookupDestination(java.lang.String jndiName)
                                 throws javax.naming.NamingException

Parameters:

jndiName - The JNDIName of the JMS destination.

Returns:

An instance of Destination

Throws:

java.lang.IllegalStateException - if the first onDestinationsAvailable() callback has not been called.

javax.naming.NamingException - if the lookup is not successful.

Excluded in public API Reference.

Look up the JMS destination using the right subject based on the JNDI properties and destination JNDI name provided in the register call.

This method should not be called before the first onDestinationsAvailable() is received by the listener of this registration.

The lookup will be done using the JNDI context that the JMSDestinationAvailabilityHelper has established with the server on behalf of the right subject. If security credentials are provided in the JNDI properties when the registration is made with the JMSDestinationAvailabilityHelper, these credentials will be used. Otherwise, the original subject that is on the application thread when the registration is made will be used unless the JMS destination is running in a different WLS domain. In the cross-domain case, the anonymous subject is used, instead of the original subject. If the listener is running on a WLS and the resultant subject is server identity, anonymous credentials will be used.

runAs

java.lang.Object runAs(java.security.PrivilegedExceptionAction action)
                throws java.security.PrivilegedActionException

Parameters:

action - An instance of PrivilegedExceptionAction.

Throws:

java.lang.IllegalStateException - if the first onDestinationsAvailable() callback has not been called.

java.security.PrivilegedActionException - if the action failed.

Excluded in public API Reference.

Perform the action and access JMS resources with the right subject based on the JNDI properties and destination JNDI name provided in the register call.

This method should not be called before the first onDestinationsAvailable() is received by the listener of this registration. The action will be done on behalf of the right subject, especially for cross WLS domain scenarios using Foreign JMS Server configuration.

The security credentials that are used to perform the action is determined as follows: 1. if the JMS destination is wrapped in a foreign JMS server configuration and the security credentials are provided in the JNDI properties, the foreign JNDI credentials in Foreign JMS Server configuration is used. 2. otherwise, if security credentials are provided in the JNDI properties when the registration is made with the JMSDestinationAvailabilityHelper, these credentials will be used unless the JMS destination is running in a different WLS domain. In the cross-domain case, the anonymous subject is used, instead of the original subject. 3. Otherwise, the original subject that is on the application thread when the registration is made will be used unless the JMS destination is running in a different WLS domain. In the cross-domain case, the anonymous subject is used, instead of the original subject. 4. If the listener is running on a WLS and the resultant subject is server identity, anonymous credentials will be used.