Daniel: Look at it from this perspective. The bean is just accepting calls from a message system. Those calls are pretty much the same thing that you get from an independent client call, except they come from messages and not client initiated code.
So, how the messages get processed is a question for the "caller", which in this case is the message system. If the message system has only a single thread that is taking messages and calling the beans, the messages will be processed "in order". If it has multiple threads, they will be processed concurrently. The number of threads determines how many concurrent calls are made. Does that help? Jonathan daniel legziel wrote: > > Jonathan: > > You said that MDBs can either process messages in batch or concurrently. I > don't see how these two processes negate each other. In my mind I just see > the MOM sending a load of messages to an instance and the instance taking > care of individualization. I could just as well see another thread doing the > same (with all the new messages that have arrived) on another instance. > > Thanks a bunch > > Daniel > > _________________________________________________________________ > Send and receive Hotmail on your mobile device: http://mobile.msn.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". -- Jonathan Baker Senior Architect eBusiness Division Sybase, Inc. [EMAIL PROTECTED] +1 301 896 1363 =========================================================================== 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".
