Hi,
>
>> -            //savedException = ex;
>> -            throw new Error(ex.getNextException().getMessage());
>> +            String message = ex.getLocalizedMessage();
>> +            Throwable nextT = ((SQLException)ex).getNextException();
>> +            if (nextT != null) message = message + "\n" + 
>> nextT.getLocalizedMessage();
>> +            throw new Error(message);
> Michael,
>
> wouldn't you have to loop over it until there is no next exception anymore? 
> or, do i misunderstand the concept here?
I see. I just reused a piece of code and noticed that the valuable SQL 
message
was in the next message.
Maybe we can get more information adding next message iteratively.
I'll try it and report.

Michaël
>
> ..ede
>
> ------------------------------------------------------------------------------
> Precog is a next-generation analytics platform capable of advanced
> analytics on semi-structured data. The platform includes APIs for building
> apps and a phenomenal toolset for data science. Developers can use
> our toolset for easy data analysis & visualization. Get a free account!
> http://www2.precog.com/precogplatform/slashdotnewsletter
> _______________________________________________
> Jump-pilot-devel mailing list
> Jump-pilot-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>
>


------------------------------------------------------------------------------
Precog is a next-generation analytics platform capable of advanced
analytics on semi-structured data. The platform includes APIs for building
apps and a phenomenal toolset for data science. Developers can use
our toolset for easy data analysis & visualization. Get a free account!
http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Reply via email to