Hi Jeff,
This is because the stack trace is transient. So it is not send over the
network (even
in local rmi calls). For example if you have a session that call's an
entity, and you
catch an entity exception in the session, the stack trace doesn't hold
state. I recall an article in javaworld (www.javaworld.com) from serverall
months ago
explaining how to make exceptions that do provide serializable stack trace.
Greetings Wim Veninga.
Jeff Schnitzer wrote:
> 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]>
