[CAMEL-4877] API-breaking changes in Validator-component

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.9.0
• Fix Version/s: 2.9.1, 2.10.0
• Component/s: camel-core
• Estimated Complexity: Unknown
• Assignee: Claus Ibsen
• Reporter: Johan Mörén
• Created: 09/Jan/12 14:55
• Updated: 19/Jan/12 07:13
• Resolved: 19/Jan/12 05:35

Description

Hi, we tried to upgrade to 2.9.0 last week but ran into trouble when using the newly moved validator component.

Before upgrading (running 2.8.0), having a root xsd that imported or included other xsd-files on the class-path was no problem for us. But upgrading to 2.9.0 breaks this functionality. Resulting in the following error

...
Caused by: org.apache.camel.ResolveEndpointFailedException: Failed to resolve endpoint: validator://com/yyy/infra/applications/yyy-application/consumer/ws/consumer-report-request.xsd due to: src-resolve: Cannot resolve the name 'ns6:YyyReport' to a(n) 'element declaration' component.
...

I can see in the new documentation for the validator-component that there is an new property that you can set called resourceResolver. Given the name and the description of the interface LSResourceResolver my guess is that an implementation of that interface is required to get the old functionality back.

I might be wrong, but to me this is API-breaking. It would be great if you could provide a "defalut" resourceResolver to mimic the old behavior since we rely a lot on the ability to compose schemas via includes or imports.