- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
Getting Exception message out
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
07-16-2012 04:24 AM
Hi
I am using Blaze 6.10.2
and I have Entrypoint that surround by try & catch
How can I get the Exception message out to the user?
Currently I have only the Exception Type as in the Catch statement it.class.simpleName
How can I get the Actual message?
The Blaze doesn't Open a intelisence on the It inside the Message.
Thanks
Yoav
Solved! Go to Solution.
Re: Getting Exception message out
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Not the Solution
- Email to a Friend
- Report Inappropriate Content
07-17-2012 06:43 PM
Hi,
Try this logic
try{
// your code
}
catch an Exception with {
sup is a NdWrappedExceptionSupport .
return " Exception text:" sup.getMessage(it).
}
Re: Getting Exception message out
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Not the Solution
- Email to a Friend
- Report Inappropriate Content
08-28-2012 09:09 AM
Sorry for going off topic, but do you know where to find a changelog of BA .NET 6.10.1 vs 6.10.2 ? I was not aware that 6.10.2 had been released.
Re: Getting Exception message out
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Accept as Solution
- Email to a Friend
- Report Inappropriate Content
09-06-2012 12:28 AM
I am using java version
sorry
Re: Getting Exception message out
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Not the Solution
- Email to a Friend
- Report Inappropriate Content
09-20-2012 07:03 AM
Other than the inner exception extraction trick, does anyone have suggestions for ways to debug wrapped "java.io.StreamCorruptedException" that do not have any more detailed error message than "The stream is corrupted"?
I assume it is related to differences in assemblies loaded in compilation vs. assemblies loaded when running the rule service, but it is very hard to debug.

