Red Hat Bugzilla – Bug 1031156
Fuse routes editor should not be in open with list for switchyard.xml files
Last modified: 2018-03-29 17:53:00 EDT
"Fuse Tooling Routes Editor" is listed in "Open With" list for switchyard.xml files. The routes editor should be constrained to applicable files.
Steps to reproduce:
1. Create a SwitchYard project
2. right-click switchyard.xml file in navigator and select "Open With"
Notice Fuse Tooling Routes Editor is in the list. If you click on this, it spins for a while then an editor with an empty canvas is opened.
How did this get assigned to me? :-)
Rob - you filed this issue. Is it important enough to fix for FSW 6?
I don't think so. It should be routed to the Fuse folks though.
Please create a Fuse Jira and link them. Thanks!
Created and linked FUSETOOLS JIRA.
Paul Leacu <email@example.com> updated the status of jira FUSETOOLS-1139 to Resolved
I couldn't eliminate the fuse camel route editor from the workbench/ project explorer pull-down targeting the switchyard.xml file since it was registered by supported extension (xml) and the OpenWithMenu method was not extendable. There was also no supported XML to exclude a particular file. Consequently - added a check to the RiderDesignEditor to issue a warning dialog if it encounters a 'switchyard.xml' file and then default to the source editor (design editor is always empty). The source editor will work.
If the user specifies a different editor for the switchyard.xml it will be retained as a preference and double-clicking switchyard.xml will invoke the editor of their choosing.
Fix will appear in Fuse Tooling 7.3
I would have guessed that you could have associated the editor with a content-type, whereby the content-type is defined using one of the xml parsers to determine the actual file type. You can look at the SwitchYard editor for an example: it edits only xml files that are rooted with a "switchyard" element.
Tomáš Sedmík <firstname.lastname@example.org> updated the status of jira FUSETOOLS-1139 to Closed