I have done simple tests using MQSeries from within a
WebLogic deployed bean. -Seems to work fine putting a
message on one queue, legacy app gets invoked and puts
message on another queue, then code in the bean gets
the message.
I'm concerned that there may be some thread management
that will rear its ugly head in the MQSeries code
--EJB beans are not supposed to do thread management.
Does anyone know if there are gotcha's here? I am not
going to do anything fancy like subscribe to all new
messages.
(Using MQSeries to link together legacy apps with EJB
seems like a natural. Using it to link in XML for new
apps seems like a good fit too. So hoping that
someone out there has had some experience with
MQSeries + EJB that they can share.)
Thanks for any info,
- Mark
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
===========================================================================
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".
