Why not have the listener be a client to the session bean? This way, no
violation.
Kirk
-----Original Message-----
From: Ashwin Dinakar <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Thursday, November 25, 1999 3:38 PM
Subject: EJB and JMS Integration Issues
>I like to continue this discussion. Currently I am using WebLogic as an EJB
server. WebLogic does provide JMS. I am thankful for that.
>
>I am still vague about how JMS is a replacement for threads in EJB.
>
>Here is a question I have.
>
>I want a producer to post a message to a queue. I want this message to be
picked up asynchronously.
>In order to accomplish this I want to wait inside a method .
>
>I want this wait() method to be invoked with a Bean (mostly a session
bean).
>
>According to the Java specification this wait() must be inside a
synchronized block (no compile time errors but a
IllegalMonitorStateException will be thrown at run-time). Is this a
violation of the EJB specification since I am using the keyword
"synchronized" within my EJB class.
>
>I am having the SessionBean class implement the MessageListener interface.
>Therefore it will implement the onMessage(String msg) method. This
onMessage will be invoked by another Thread-call back thread.
>
>Ashwin.
>
>===========================================================================
>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".
===========================================================================
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".
