By connection pool I mean a pool of MQQueueManager objects that are connected to a
queue manager. I may have a pool of MQQueueManager/MQQueue tuples for performance
reasons which are related to the MQSeries java interface. I'm not very concerned with
the details right now, but simply how do I make any such set of information available
to a bean.
I didn't even want to mention the issue about transaction support for MQSeries,
because as you mention there is no JTS support in MQ. We are going to have a few
issues there as well. One thing at a time :)
>>> <[EMAIL PROTECTED]> 08/13 12:25 PM >>>
When you mean a MQSeries connection, you mean a pool of open MQSeries queue
managers/queues? When you say "For our entity beans we will be using MQSeries
with BMP", I take you mean the commital of a message to the queue? Or were you
talking about wrapping the put/get as a transaction? Until MQSeries supports
JTS, I don't think you can wrap a complete put/get in a single transaction.
Perry Hoekstra
[EMAIL PROTECTED]
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
