Bug 1046037 - Whole stack present in server log if constraint editor cannot parse condition.
Summary: Whole stack present in server log if constraint editor cannot parse condition.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: jBPM Designer
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ER1
: 6.0.1
Assignee: Jan
QA Contact: Marek Baluch
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-23 10:43 UTC by Marek Baluch
Modified: 2014-08-06 20:03 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-08-06 20:03:56 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
stack-trace (5.66 KB, text/plain)
2013-12-23 13:55 UTC, Marek Baluch 		no flags Details
View All

Description Marek Baluch 2013-12-23 10:43:07 UTC 
Description of problem:
When the condition set on a sequence flow cannot be parsed by the constraint editor then the whole stack trace will be present in the server log. This potentially presents a lot of waste in the log. Please consider outputting only an error message or changing the log level.

Steps to Reproduce:
1. Create a sequence flow condition which does not have the format of 'KieFunctions.functionName(variable, params)'
2. Switch to the constraint editor.
3. Take a look into the server log
Comment 1 Marek Baluch 2013-12-23 13:55:37 UTC 
Created attachment 840800 [details]
stack-trace
Comment 2 Marek Baluch 2014-01-07 12:54:38 UTC 
Lowering severity as this issue represents a clear enhancement.
Comment 3 Jan 2014-01-15 16:43:46 UTC 
Fixed in master: http://github.com/droolsjbpm/jbpm-designer/commit/2c46d9d79
Comment 4 Jan 2014-01-23 12:28:16 UTC 
Cherry-picked into 6.0.x: http://github.com/droolsjbpm/jbpm-designer/commit/bf428084d
Comment 5 Marek Baluch 2014-02-17 12:38:06 UTC 
Verified on 6.0.1.ER1.
Note You need to log in before you can comment on or make changes to this bug.