This content has been marked as final.
Show 4 replies
-
1. Re: AbstractInstancePool.java is eating up exceptions
starksm64 Jun 29, 2005 2:00 AM (in response to clebert.suconic)That looks fine to me. There is no reason to throw an EJBException without the actual cause.
-
3. Re: AbstractInstancePool.java is eating up exceptions
deb.beaman Jun 29, 2005 1:38 PM (in response to clebert.suconic)I assume I will have to back port it to 3.2.X also, right?
What about HEAD, should I commit this small change there also?
Clebert -
4. Re: AbstractInstancePool.java is eating up exceptions
adrian.brock Jun 29, 2005 1:46 PM (in response to clebert.suconic)You should always forward port any fix.
Backporting is upto you. 3.2.x is in maintenance mode which means that only
must have fixes like security problems or those requested by customers
absolutely have to be backported.