> See manual section 4.1 re: getNextException() -- Jess is telling you > that it called a Java method via reflection, and it threw an > exception. You have to call getNextException.printStackTrace() to see > it -- it will probably give you a clue!
Would it be more appropriate for Jess to throw an InvocationTargetException, or an exception deried from it, instead? Jess must be trapping this exception internally (I don't have the source handy) and then copying getTargetException() into setNextException(). What is the reason for doing this? Just curious... I suspect that it may be too late to change this behavior since many people already rely on the current exception. alan -------------------------------------------------------------------- To unsubscribe, send the words 'unsubscribe jess-users [EMAIL PROTECTED]' in the BODY of a message to [EMAIL PROTECTED], NOT to the list (use your own address!) List problems? Notify [EMAIL PROTECTED] --------------------------------------------------------------------
