I must say that it is incorrect. in ejb 1.0, EJBException used to be a
checked exception. in ejb 1.1, it is a run time exception. hence the
container behaviour is the same for both. it will destroy the components
SQLexception is a checked exception. it will not cause the container to
destroy the objects. unless rollbackonly is set, the transaction can be
committed as well.
> -----Original Message-----
> From: Kenneth D. Litwak [mailto:[EMAIL PROTECTED]]
> Sent: Monday, June 19, 2000 4:11 PM
> To: [EMAIL PROTECTED]
> Subject: Two Exception questions
>
>
> I'm getting conflicting opinions and don't hae the spec
> handy. SO, in EJB
> 1.1, if you throw an EJBException, the container does not destory your
> bean,while if the container throws a run-time exception and
> that goes tot he
> caller, the container will destory your bean, right?
>
> For the above, an SQLException would or would not cause the
> container to trash
> the bean?
>
> Thanks.
>
>
>
> Ken
>
> ==============================================================
> =============
> 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".
