[
http://jira.jboss.com/jira/browse/JBPM-453?page=all ]
Thomas Diesler resolved JBPM-453.
---------------------------------
Resolution: Out of Date
Refactor Timer.getException() to return an Exception
----------------------------------------------------
Key: JBPM-453
URL:
http://jira.jboss.com/jira/browse/JBPM-453
Project: JBoss jBPM
Issue Type: Feature Request
Components: Core Engine
Affects Versions: jBPM 3.0.1
Reporter: Rainer Alfoeldi
Assigned To: Tom Baeyens
If an Exception occurs during the execution of a Timer the first 4000 characters of the
DelegationException.printStackTrace() output is saved and the Exception itself is
disgarded.
Is it possible to extend Timer to return the caught Exception? The getException() will
probably have to stay unchanged, but a new method would be very welcome.
The background for this request is if error handling is done outside of the Timer / jBPM
Workflow execution there is no way of securely finding out what really caused the problem.
The root cause MIGHT be mentioned in the first 4000 characters but that is not sure. And
even if it is mentioned you would have to start parsing the returned String. StackTraces
differ from JVM to JVM etc. etc. Not a fun thing to do.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira