openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Linskey" <plins...@bea.com>
Subject RE: RollbackException.toString()
Date Tue, 31 Oct 2006 09:39:44 GMT
Our internal testing framework, in this case, is vanilla JUnit. Seems
like that might be a use case that we should care about, no?

-Patrick

-- 
Patrick Linskey
BEA Systems, Inc. 

_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it. 

> -----Original Message-----
> From: Abe White 
> Sent: Monday, October 30, 2006 4:06 PM
> To: open-jpa-dev@incubator.apache.org
> Subject: Re: RollbackException.toString()
> 
> > What is this 'inner exception' that you speak of? The underlying
> > exception is set to the cause, but the cause is not being printed.
> >
> > IOW, I get all the information I need when I do an 
> e.printStackTrace()
> 
> OK, that's how it should be then.  I don't want to deviate from  
> Java's standard Exception.toString() behavior for all users just  
> because our internal testing harness happens to be braindead about  
> reporting errors.
> 

Mime
View raw message