I have wriiten an ejb application that uses bmp entity beans. Some of these beans have
multiple sql methods that are run in the ejbStore, ejbLoad methods etc. I was
originally handling of the commits and rollbacks myself within the bean. With the
release of the j2ee reference implementation and the final ejb 1.1 spec I have
discovered that the handling of commits and rollbacks is not allowed in the bean
iteself and that this is controlled by the container. This makes sense to me but I
have not been able to figure out how you let the container know that a sql statement
has failed and that a rollback needs to be performed. From reading the spec and
looking at some of the example code made available with the j2ee ri the only thing I
can see is to catch the SQLException within the bean code and package it up as an
EJBException and then throw it back to the container. I am assumming then that the
container will see that a SQLException is contained in the thrown EJBException and cal!
l rollback on the connection. I couldn't find anything in the spec that really covered
this is detail although I must admit I didn't read it from end to end (I really should
though :->)
My question is :
Is this the behavior that bmp entity bean coders can expect from EJB Server/Container
vendors ?
===========================================================================
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".
