Bug 1031156
| Summary: | Fuse routes editor should not be in open with list for switchyard.xml files | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Fuse Service Works 6 | Reporter: | Rob Cernich <rcernich> |
| Component: | Camel | Assignee: | Nobody <nobody> |
| Status: | CLOSED UPSTREAM | QA Contact: | Matej Melko <mmelko> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.0.0 | CC: | soa-p-jira |
| Target Milestone: | ER1 | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
The "Fuse Tooling Routes Editor" is present in the "Open With" list for switchyard.xml files. The Routes Editor should be constrained to applicable files. If you attempt to click it, an empty canvas is opened. To work around this issue, avoid clicking on this option.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2025-02-10 03:34:23 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Rob Cernich
2013-11-15 18:10:22 UTC
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 <pleacu> updated the status of jira FUSETOOLS-1139 to Resolved https://github.com/fusesource/fuseide/commit/afc1686cab7999eb5466286dfe514086d9246b77 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 <tsedmik> updated the status of jira FUSETOOLS-1139 to Closed This product has been discontinued or is no longer tracked in Red Hat Bugzilla. |