Description of problem: When creating new SwitchYard projects, the user must always turn off "Honor All Schema Locations" in the XML preferences by hand for the project. Instead, we should flip this preference to false in the m2e configurator when the project is created. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Brian Fitzpatrick <bfitzpat> made a comment on jira SWITCHYARD-1779 This came out of the usability review but has been an issue with the tooling for a while. We put the code to disable "Honour All Schema Locations" into the facet installation class so it gets triggered the first time a project is created (i.e. "New SwitchYard Project") and when it is imported (i.e. importing an existing project via the m2e import wizard in Eclipse). What happens is that the project's "Validation->XML Syntax" settings are updated to override the workbench-wide setting for Honor all Schema. "Enable Project Specific Settings" is checked and "Honor all XML schema locations" is unchecked. Note that if the facets have already been created, the change is not made. And note that if the "Honor all schema locations" box is unchecked in the workbench settings, the change is not made to the project settings.
Rob Cernich <rcernich> made a comment on jira SWITCHYARD-1779 pushed i modified the test plugins to not disable this setting globally to test that the setting is being disabled for switchyard projects, which it is.
Rob Cernich <rcernich> updated the status of jira SWITCHYARD-1779 to Reopened
Rob Cernich <rcernich> made a comment on jira SWITCHYARD-1779 Hey Brian, Can you validate that this works when installed in JBT or JBDS? I installed the latest SY into JBDS and was getting XML errors in the switchyard.xml file. The setting is disabled in the project specific preferences, but enabled for the workspace. The only way the errors go away is when I disable the workspace setting. I'm not sure what the difference is between testing locally and testing when installed in JBDS. Thanks in advance, Rob
Rob Cernich <rcernich> made a comment on jira SWITCHYARD-1779 It appears the problem may be related to the XHTML validator contributed by the JSF tools. Disabling the XHTML validator seems to make the problem go away. I haven't investigated any further than this.
Brian Fitzpatrick <bfitzpat> made a comment on jira SWITCHYARD-1779 Huh. That's weird, but I can take a look.
Brian Fitzpatrick <bfitzpat> made a comment on jira SWITCHYARD-1779 Downloading the latest JBDS to check it out in a bit.
Brian Fitzpatrick <bfitzpat> made a comment on jira SWITCHYARD-1779 Created JBIDE-15819 to address the XHTML Validator problem from the JSF tools. Will create a new pull request to override the workbench-level "Honour all XML schema locations" setting for now and we can roll it back to a project level setting when it gets fixed.
Brian Fitzpatrick <bfitzpat> made a comment on jira SWITCHYARD-1779 Added new PR - https://github.com/jboss-switchyard/tools/pull/336 - to address issue with XHTML Validator (JBIDE-15819)
Rob Cernich <rcernich> made a comment on jira SWITCHYARD-1779 pushed second PR
Victor Rubezhny <ruby> made a comment on jira SWITCHYARD-1779 Cannot log in to RH-bugzilla, so posting it here. The switchyard1779.patch proposes the code I've used to test the fix for the issue [JBIDE-15819|https://issues.jboss.org/browse/JBIDE-15819]. This patch restores the project-level preferences to be used instead of workspace-level preferences and adds flushing of new preference values upon a project creation. This patch return to is to be applied not earlier than the fix for [JBIDE-15819|https://issues.jboss.org/browse/JBIDE-15819] will be resolved. Thanks again for a great catch!
Victor Rubezhny <ruby> made a comment on jira SWITCHYARD-1779 Cannot log in to RH-bugzilla, so posting it here. The switchyard1779.patch proposes the code I've used to test the fix for the issue [JBIDE-15819|https://issues.jboss.org/browse/JBIDE-15819]. This patch restores the project-level preferences to be used instead of workspace-level preferences and adds flushing of new preference values upon a project creation. This patch is to be applied not earlier than the fix for [JBIDE-15819|https://issues.jboss.org/browse/JBIDE-15819] will be resolved. Thanks again for a great catch!
Verified with JBDS-IS 7.0.0.CR1
Keith Babo <kbabo> updated the status of jira SWITCHYARD-1779 to Closed