Description of problem: Warnings/Errors found in JBDS "Problems" View, right after quickstart is imported as maven project. steps to reproduce: 1. Start JBDS 2. import existing maven project 3. Window / Show View / Problems 4. check for errors Actual results: Required transformation missing: from="java:java.lang.String" to="{urn:switchyard-quickstart:validate-xml:0.1.0}orderAck". switchyard.xml /switchyard-quickstart-validate-xml/src/main/resources/META-INF Unknown SwitchYard Required transformation missing: from="{urn:switchyard-quickstart:validate-xml:0.1.0}order" to="java:java.lang.String". switchyard.xml /switchyard-quickstart-validate-xml/src/main/resources/META-INF Unknown SwitchYard schema_reference.4: Failed to read schema document 'orders.base', because 1) could not find the document; 2) the document could not be read; 3) the root element of the document is not <xsd:schema>. orders.xsd /switchyard-quickstart-validate-xml/src/main/resources/xsd line 6 XML Schema Problem src-resolve: Cannot resolve the name 'base:order.base' to a(n) 'element declaration' component. orders.xsd /switchyard-quickstart-validate-xml/src/main/resources/xsd line 8 XML Schema Problem Unused Capability: The "Camel Route" capability is configured on the project, but is not required by any SwitchYard binding or implementation types used in the project. switchyard.xml /switchyard-quickstart-validate-xml/src/main/resources/META-INF Unknown SwitchYard Expected results: No warnings/errors in JBDS Additional info:
Brian Fitzpatrick <bfitzpat> made a comment on jira SWITCHYARD-1652 Patch fixes the unnecessary component reference in the pom
Brian Fitzpatrick <bfitzpat> made a comment on jira SWITCHYARD-1652 PR removes unneeded camel component from pom, which eliminates the warning seen when importing the project in the tooling. The transformation errors will be resolved by the PR for SWITCHYARD-1654.
Rob Cernich <rcernich> made a comment on jira SWITCHYARD-1654 pushed
Keith Babo <kbabo> made a comment on jira SWITCHYARD-1652 pushed
After importing the quickstart 'validate-xml' there are the following error: src-resolve: Cannot resolve the name 'base:order.base' to a(n) 'element declaration' component. in /switchyard-quickstart-validate-xml/src/main/resources/xsd/orders.xsd
It appears the schemaLocation attribute for the imported base schema in orders.xsd is set to orders.base where I think it should be orders-base.xsd.
Andrej, I am also seeing the issue with the orders.xsd when I import using the most recent version of the SwitchYard tooling. This has nothing to do with the SY tooling itself and something to do with how Eclipse is validating the use of the XML Catalog element. Even if I import the catalog as provided by the quickstart into Eclipse (File->Import, XML->XML Catalog) it's not finding the order.base for the substitution group. This is going to require some further investigation I'm afraid.
The remaining issue is not related to the tooling. As I stated above, the issue can be fixed by updating the schemaLocation attribute from orders.base to orders-base.xsd (i.e. change it to the actual schema location).
That's true, but then the quickstart doesn't run for me. It fails with errors.
You'll need to update the catalog file as well. Or...Instead of updating the XSD, you could update the readme to tell users to add the catalog file packaged with the quickstart to their list of catalogs (preferences, XML->XML Catalog, then add a catalog entry, specifying the catalog in the xsd folder).
Brian Fitzpatrick <bfitzpat> updated the status of jira SWITCHYARD-1652 to Reopened
Brian Fitzpatrick <bfitzpat> made a comment on jira SWITCHYARD-1652 Reopening to address some XML validation errors
Brian Fitzpatrick <bfitzpat> made a comment on jira SWITCHYARD-1652 Patch fixes the schema validation errors.
Rob or Brian, could you describe me what's the correct workaround, please?
Andrej, I think you need to add src/main/resources/xsd/catalog.xml to your XML Catalog preferences (Window->Preferences..., under XML). This will allow the Eclipse XML validator to resolve the schemaLocation, orders.base. In other words, you need to configure Eclipse to use the same catalog file that the runtime will use during execution. Hope that helps.
Keith Babo <kbabo> updated the status of jira SWITCHYARD-1654 to Closed
Updated the quickstart to remove errors/warnings. Added instructions to the Readme on how to configure the XML catalog in eclipse.
Douglas Palmer <dpalmer> updated the status of jira SWITCHYARD-2385 to Reopened