Bug 1062691

Summary:	[GSS] (6.2.x) Schema validation + multiple schema imports in same namespace + catalog lookup doesn't work
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Kyle Lape <klape>
Component:	Web Services	Assignee:	Alessio Soldano <asoldano>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Rostislav Svoboda <rsvoboda>
Severity:	unspecified	Docs Contact:	Russell Dickenson <rdickens>
Priority:	unspecified
Version:	6.2.1	CC:	klape, psakar, sjaakderksen, smumford, vtunka
Target Milestone:	CR2
Target Release:	EAP 6.2.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
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.	Story Points:	---
Clone Of:	1060355	Environment:
Last Closed:	2014-06-02 12:50:34 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:
Bug Depends On:
Bug Blocks:	1040729

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.