Bug 1128355 - Imports in WorkItemDefinition are not validated
Summary: Imports in WorkItemDefinition are not validated
Keywords:
Status: ASSIGNED
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: jBPM Designer
Version: 6.0.2
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Tihomir Surdilovic
QA Contact: Kirill Gaevskii
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-09 11:08 UTC by Anton Giertli
Modified: 2016-01-08 21:46 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)

Description Anton Giertli 2014-08-09 11:08:10 UTC
Description of problem:

Validation of the imports in the work item definition is not performed.


Version-Release number of selected component (if applicable):
bpm 6.0.2

How reproducible:

always

Steps to Reproduce:
1. Open the default WorkItemDefinition file which gets created when you create new process in business-central
2. To whatever workitem add this parameter


  "port" : new IntegerDataType()

And **don't** include 
import org.drools.core.process.core.datatype.impl.type.IntegerDataType;

Save and Validate  - everything seems successful
3. open the process definition, and the Service Tasks tab from the Object Library is completely missing!
4. Following error can be observer in the server.log

12:59:22,262 ERROR [org.jbpm.designer.web.preprocessing.impl.JbpmPreprocessingUnit] (http-localhost/127.0.0.1:8080-1) Unable to parse a workitem definition: [Error: unable to resolve class: IntegerDataType from [Module "deployment.business-central.war:main" from Service Module Loader]]
[Near : {... "port" : new IntegerDataType(), ....}]
                          ^
[Line: 63, Column: 20]

Actual results:

Imports in the WorkItemDefinition are not validated and causing subsequent issues in the Designer.

Expected results:

Imports in the WorkItemDefinition are validated.


Additional info:


Note You need to log in before you can comment on or make changes to this bug.