Bug 1048173 - Designer produces XSD-invalid process XML if any node has zero X or Y coordinate
Summary: Designer produces XSD-invalid process XML if any node has zero X or Y coordinate
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: jBPM Designer
Version: unspecified
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-01-03 10:19 UTC by Jiri Locker
Modified: 2020-03-27 19:02 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-27 19:02:41 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1156457 0 medium CLOSED ExtensibleXmlParser Error 2021-02-22 00:41:40 UTC

Internal Links: 1156457

Description Jiri Locker 2014-01-03 10:19:43 UTC
Description of problem:
In such case the "x" or "y" attribute of Bounds element in BPMNDiagram section is omitted, however these attributes are required as seen here https://github.com/worktokenteam/worktoken/blob/master/bpmn/DC.xsd. Having such process in the project produces error log messages on each project build:

11:01:11,187 ERROR [org.drools.core.xml.ExtensibleXmlParser] (pool-13-thread-1) (null: 58, 48): cvc-complex-type.4: Attribute 'x' must appear on element 'dc:Bounds'.

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

How reproducible:
-

Steps to Reproduce:
1. open existing process
2. move Start node to the left border of designer canvas
3. save the process (error is logged)
4. build the project to repeat the error message in server log

Actual results:
"x" attribute in Bounds element related to the start node is missing. XML validation error is logged.

Expected results:
"x" attribute should be present and set to "0.0" to keep the process XML valid.

Additional info:


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