You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the issue
Right now the JMS Facade is a bit messy with both the MessagingSource, MessagingSourceFactory and the Facade doing JMS related things. The code should be cleaned up and tested. A check should be performed if the QCF is wrapped in a TransactionAwareConnectionFactoryProxy and like the TransactionalDbmsSupportAwareDataSourceProxy the metadata should be cached.
Also both MessagingSource#getPhysicalName() and JmsMessagingSourceFactory#getConnectionFactoryInfo(...) have methods to retrieve info about the QCF.
Wrapping the QCF in JmsMessagingSourceFactory should be moved to the QueueConnectionFactoryFactory.
The toString info, changed in pr #4481 and #4572 need to work as well...
Reporter
Niels
The text was updated successfully, but these errors were encountered:
Describe the issue
Right now the JMS Facade is a bit messy with both the MessagingSource, MessagingSourceFactory and the Facade doing JMS related things. The code should be cleaned up and tested. A check should be performed if the QCF is wrapped in a
TransactionAwareConnectionFactoryProxy
and like theTransactionalDbmsSupportAwareDataSourceProxy
the metadata should be cached.Also both
MessagingSource#getPhysicalName()
andJmsMessagingSourceFactory#getConnectionFactoryInfo(...)
have methods to retrieve info about the QCF.Wrapping the QCF in
JmsMessagingSourceFactory
should be moved to theQueueConnectionFactoryFactory
.The toString info, changed in pr #4481 and #4572 need to work as well...
Reporter
Niels
The text was updated successfully, but these errors were encountered: