Package org.frankframework.jms
Class JmsMessagingSourceFactory
java.lang.Object
org.frankframework.jms.AbstractMessagingSourceFactory
org.frankframework.jms.JmsMessagingSourceFactory
Factory for
JmsMessagingSource
s, to share them for JMS Objects that can use the same.
JMS related IBIS objects can obtain a MessagingSource from this class. The physical connection is shared between all IBIS objects that have the same connectionFactoryName.
- Since:
- 4.4
- Author:
- Gerrit van Brakel
-
Field Summary
Fields inherited from class org.frankframework.jms.AbstractMessagingSourceFactory
log
-
Constructor Summary
-
Method Summary
Modifier and TypeMethodDescriptionprotected jakarta.jms.ConnectionFactory
createConnectionFactory
(Context context, String cfName, boolean createDestination) Removed the suggested wrap ConnectionFactory, to work around bug in JMSQueueConnectionFactoryHandle in combination with Spring.protected Context
protected MessagingSource
createMessagingSource
(String jmsConnectionFactoryName, String authAlias, boolean createDestination) getConnectionFactoryInfo
(jakarta.jms.ConnectionFactory connectionFactory) protected Map<String,
MessagingSource> Methods inherited from class org.frankframework.jms.AbstractMessagingSourceFactory
getConnectionFactory, getContext, getMessagingSource
-
Constructor Details
-
JmsMessagingSourceFactory
-
-
Method Details
-
getMessagingSourceMap
- Specified by:
getMessagingSourceMap
in classAbstractMessagingSourceFactory
-
createMessagingSource
protected MessagingSource createMessagingSource(String jmsConnectionFactoryName, String authAlias, boolean createDestination) throws IbisException - Overrides:
createMessagingSource
in classAbstractMessagingSourceFactory
- Throws:
IbisException
-
createContext
- Specified by:
createContext
in classAbstractMessagingSourceFactory
- Throws:
NamingException
-
createConnectionFactory
protected jakarta.jms.ConnectionFactory createConnectionFactory(Context context, String cfName, boolean createDestination) throws IbisException Removed the suggested wrap ConnectionFactory, to work around bug in JMSQueueConnectionFactoryHandle in combination with Spring. This was a bug in WAS 6.1 in combination with Spring 2.1, taking a risk here, but I'm assuming WebSphere has fixed this by now. see https://web.archive.org/web/20130510092515/http://forum.springsource.org/archive/index.php/t-43700.html- Specified by:
createConnectionFactory
in classAbstractMessagingSourceFactory
- Throws:
IbisException
-
getConnectionFactoryInfo
-