Bug 1062691 - [GSS] (6.2.x) Schema validation + multiple schema imports in same namespace + catalog lookup doesn't work
Summary: [GSS] (6.2.x) Schema validation + multiple schema imports in same namespace +...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web Services
Version: 6.2.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR2
: EAP 6.2.2
Assignee: Alessio Soldano
QA Contact: Rostislav Svoboda
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks: 1040729
TreeView+ depends on / blocked
 
Reported: 2014-02-07 17:52 UTC by Kyle Lape
Modified: 2018-12-04 17:22 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
A bug that caused the catalog lookup to fail has been resolved in this release of JBoss EAP. In previous versions of the product, if schema validation was enabled, catalog validation returned only the first schema found when WSDL references multiple schemas. This could cause the catalog lookup to fail. In this release of the product, catalog lookup now resolves on the filename before falling back to namespace-only resolution. As a result, catalog validation no longer fails.
Clone Of: 1060355
Environment:
Last Closed: 2014-06-02 12:50:34 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Apache JIRA CXF-5532 0 None None None Never

Description Kyle Lape 2014-02-07 17:52:25 UTC 
+++ This bug was initially created as a clone of Bug #1060355 +++

Catalog lookup is enabled to prevent requests to third party servers, and the third party schema referenced in the WSDL references multiple schemas in the same namespace.

When schema validation is enabled, the algorithm in org.apache.cxf.wsdl.EndpointReferenceUtils.SchemaLSResourceResolver#resolveResource does not resolve the correct schema since in the above scenario it falls back to namespace-only resolution, which returns the first schema it sees.  This can be fixed by trying to resolve on only the "filename" before resorting to namespace-only resolution.
Comment 4 Scott Mumford 2014-03-10 00:23:35 UTC 
Added draft release note text.
Note You need to log in before you can comment on or make changes to this bug.