Bug 1083854 - BPMN XML generated by BPMN designer do not follow user specified XML formatting
Summary: BPMN XML generated by BPMN designer do not follow user specified XML formatting
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss BPMS Platform 6
Classification: Retired
Component: Eclipse Tooling
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Robert (Bob) Brodt
QA Contact: Jozef Marko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-03 05:58 UTC by Václav Chalupa
Modified: 2016-09-20 01:38 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-02-05 14:42:15 UTC
Type: Feature Request
Embargoed:


Attachments (Terms of Use)

Description Václav Chalupa 2014-04-03 05:58:12 UTC
Description of problem:

BPMN designer ignore user settings for XML files formatting and always use 2 spaces for indentation.

How reproducible:

Set 'Indend using tabs' (or different settings then 2 spaces) in eclipse preferences - XML Files formatting, create process with BPMN designer and see generated BPMN XML.

Actual results:

Generated BPMN XML source file has always 2 spaces for indentation.

Expected results:

Generated BPMN XML source file follows the specified XML formatting settings.

Comment 2 Robert (Bob) Brodt 2016-01-21 18:02:38 UTC
This is probably an issue in the XML serializer used by EMF. I don't think it even knows about the XML editor's preferences; not sure what I can do about that...

Comment 3 Robert (Bob) Brodt 2016-02-05 14:42:15 UTC
There are only a few XML serialization "tweaks" available through the EMF public API; these are not controlled by the XML Editor's preference settings and, as far as I can tell, none of these control whether tab or space indenting is used.

See http://download.eclipse.org/modeling/emf/emf/javadoc/2.4.2/org/eclipse/emf/ecore/xmi/XMLResource.html for more info.

Closing this BZ as Won't Fix


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