Bug 1083871

Summary:	switchyard.xml generated by SwitchYard editor do not follow user specified XML formatting
Product:	[JBoss] JBoss Fuse Service Works 6	Reporter:	Václav Chalupa <vchalupa>
Component:	SwitchYard Editor	Assignee:	Rob Cernich <rcernich>
Status:	CLOSED UPSTREAM	QA Contact:	Matej Melko <mmelko>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.0.0 GA	CC:	mvecera, oskutka, soa-p-jira
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-02-10 03:35:31 UTC	Type:	Feature Request
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Václav Chalupa 2014-04-03 06:46:00 UTC

Description of problem:

SwitchYard UI editor ignore user settings for XML files formatting and always use 2 spaces for indentation.

How reproducible:

Set 'Indent using tabs' (or different settings then 2 spaces) in eclipse preferences - XML Files formatting, design SwitchYard composite with the SwitchYard UI editor and see generated switchyard.xml.

Actual results:

Generated switchyard.xml file has always 2 spaces for indentation.

Expected results:

Generated switchyard.xml file follows the specified setting of XML formatting.

Comment 1 Brian Fitzpatrick 2014-06-09 18:18:24 UTC

Apparently there isn't a great way to handle this currently in EMF. Based on this thread in the EMF forum (http://www.eclipse.org/forums/index.php/t/340341/) it appears that we would need to specialize the serializer itself, e.g., in
org.eclipse.emf.ecore.xmi.impl.XMLString.getElementIndent(int) and pick up the correct value from the preference.

Comment 2 kconner 2014-09-02 18:31:20 UTC

*** Bug 1026391 has been marked as a duplicate of this bug. ***

Comment 9 Red Hat Bugzilla 2025-02-10 03:35:31 UTC

This product has been discontinued or is no longer tracked in Red Hat Bugzilla.