> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Aaron Mulder
> Sent: Sunday, May 28, 2000 3:21 AM
> To: jBoss Developer
> Subject: Re: [jBoss-Dev] JDBC Pools - what to do for SQLExceptions?
>
>
> On Sat, 27 May 2000, Dan OConnor wrote:
> > Hi Aaron,
> >
> > I doubt the container is doing the right thing at this point on
> > exceptions.  (I'm guessing without thinking too hard, but I feel
> > pretty sure...)  You should look at chapter 12 of the EJB 1.1 spec
> > for the correct behavior with regard to exceptions.  Basically, there
> > are two kinds: an application exception, for which you should try to
> > commit the transaction on a boundary unless it has been marked
> > for rollback only; and system exceptions, for which the transaction
> > should always be rolled back and we are responsible for cleanup of
> > any resource we can.
> >
> > By the way, the Enterprise JavaBeans specification is actually a
> > well-written and easy-to-understand document of moderate length.
> > I don't think the average bean developer needs to read it, but I think
> > the average container developer should.  :-)
>
>       Sigh.  This brings the Spec Count to 5...  I'm sure you're right.
> I'll check it out.

I must warn you,  EJB is no walk in the park.  It is very well written but
if you are not used to spec lingo, you can wander for hours in the 300
pages.  Use it as reference at first, and when you are familiar with some
part, give it a cover to cover shot...

marc

>
> > Also, I wanted to say that it sounds like you're getting up to speed
> > quickly on this project.  I can't wait to see what you come up with
> > for the connection pools, which as Marc mentioned are really a key
> > piece of the container.
> >
> > -Dan
>
>       Thank you.  More on this in my next message.
>
> Aaron
>
>
>


Reply via email to