I've noticed that the printStackTrace() method on EJBException doesn't print the trace for the nested exception. This makes debugging exceptions thrown deep within several layers of EJB's calling EJB's difficult. Is this something I should ask the Orion team to fix? Or is it something that Sun needs to take care of? For the moment I suppose I can rip the class file out of ejb.jar and add my own EJBException. Jeff Schnitzer [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
- Re: EJBException.printStackTrace() Jeff Schnitzer
- Re: EJBException.printStackTrace() wim veninga
- RE: EJBException.printStackTrace() Jeff Schnitzer