I think this is mostly in 14.4.8 of the "spec". The container automatically
will handle the ack as part of the commit in CMT. If you
are using BMT, there is an option for you to specify an acknowledgement
mode. There are two options - both of which are defined in the JMS 1.0.2
spec, sec. 4.4.13 - DUPS_OK_ACKNOWLEDGE & AUTO_ACKNOWLEDGE. I think in the
DUPS case the protocol is such that the container will acknowledge and you
can also acknowledge although I may be missing something too.
>From: Robert Nicholson <[EMAIL PROTECTED]>
>Reply-To: A mailing list for Enterprise JavaBeans development
><[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Acknowledgement with Message Driven Beans.
>Date: Sat, 3 Mar 2001 15:24:04 -0800
>
>As long as an EJB gets an onMessage call, regardless of bean managed
>transactions or container managed, is that considered to have been a
>succsessful delivery? and therefore nothing will ever get put back into the
>a queue even if system exceptions are raised? I apoligize for not having
>digested the spec already. But I'm interested in what level of Control the
>bean itself has for controlling acknowledgment receipts etc.
>
>===========================================================================
>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".
>
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.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".
