| org.springframework.jndi.JndiLocatorSupport
 org.springframework.jms.support.destination.JndiDestinationResolver
| clearCache | | public void clearCache()(Code) | | |
| removeFromCache | | public void removeFromCache(String destinationName)(Code) | | |
| resolveDestinationName | | public Destination resolveDestinationName(Session session, String destinationName, boolean pubSubDomain) throws JMSException(Code) | | |
| setCache | | public void setCache(boolean cache)(Code) | | Set whether to cache resolved destinations. Default is "true".
This flag can be turned off to re-lookup a destination for each operation,
which allows for hot restarting of destinations. This is mainly useful
during development.
Note that dynamic queues and topics get cached by destination name.
As a consequence, you need to use unique destination names across both
queues and topics.
|
| setFallbackToDynamicDestination | | public void setFallbackToDynamicDestination(boolean fallbackToDynamicDestination)(Code) | | Set whether this resolver is supposed to create dynamic destinations
if the destination name is not found in JNDI. Default is "false".
Turn this flag on to enable transparent fallback to dynamic destinations.
See Also: JndiDestinationResolver.setDynamicDestinationResolver |
| validateDestination | | protected void validateDestination(Destination destination, String destinationName, boolean pubSubDomain)(Code) | | Validate the given Destination object, checking whether it matches
the expected type.
Parameters:
destination - the Destination object to validate
Parameters:
destinationName - the name of the destination
Parameters:
pubSubDomain - true if a Topic is expected,false in case of a Queue |
| Fields inherited from org.springframework.jndi.JndiLocatorSupport | final public static String CONTAINER_PREFIX(Code)(Java Doc)
|
|
|