Besides observing that Session Bean (B) got a message, in general what other
information can a developer expect in general from the system to be able to
help debug or verify or trace that a message made its way from sender to the
MDB? Are there areas in the message system or container (e.g. stats) or
elsewhere that they should look at?
-Chris Thompson
-----Original Message-----
From: Cedric Beust [mailto:[EMAIL PROTECTED]]
Sent: Monday, August 13, 2001 10:51 AM
Subject: Re: Synchronous call to Message Driven Bean
> From: A mailing list for Enterprise JavaBeans development
> [mailto:[EMAIL PROTECTED]]On Behalf Of Singh, Harvinder (CORP,
GEITC)
> Can anybody help me with this.
> I want to make a synchronous call to a Message Driven Bean (that is
somehow
> call the onMessage() method directly from a client)
> 1) Can I do that (I am of the opinion that it won't be possible since
MDB's
> don't have a remote and home interfaces ....)
No.
> 2) If not then how can I make a synchronous call to a MDB (Since there are
a
> couple of events happening that cause the App server to call this MDB and
> then a couple of actions take place .... so I want to debug the entire
thing
> so I need to make a call to MDB directly--- primarily for debugging using
> VisualCafe)
You can't.
I suggest the following pattern: have your MDB (A) call a Session Bean (B)
and
do your business logic in B.
If you need to make a synchronous call, call B directly.
--
Cedric
===========================================================================
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".
