Bug 856600 - Imported XSDs in WSDL are rewritten wrongly by JBR Gateway
Imported XSDs in WSDL are rewritten wrongly by JBR Gateway
Status: NEW
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBossESB (Show other bugs)
5.3.0 GA
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: kconner
Depends On:
  Show dependency treegraph
Reported: 2012-09-12 07:54 EDT by Tadayoshi Sato
Modified: 2012-09-12 07:54 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
JBoss Issue Tracker JBESB-3844 Major Open Imported XSDs in WSDL are rewritten wrongly by JBR Gateway 2012-11-27 10:28:11 EST

  None (edit)
Description Tadayoshi Sato 2012-09-12 07:54:21 EDT
Description of problem:
Platform BZ for https://issues.jboss.org/browse/JBESB-3844

Turning 'cache-schemas' introduced by JBESB-3802 to true doens't rewrite the schema imports in WSDLs correctly for the JBoss Remoting Gateway. The definitions/import/@location or the definitions/types/schema/import/@schemaLocation in a WSDL should be rewritten to:
but actually:
where the JBR gateway is configured at http://localhost:8765.

How reproducible:

Steps to Reproduce:
1. Make a contract-first web service whose WSDL contains XSD imports and deploy it to SOA-P.
2. Make an ESB service which proxies the above web service using SOAPProcessor or SOAPProxy and re-publishes it through JBR Gateway/HTTP and deploy it to SOA-P.
3. Check the proxied WSDL from the contract web.

Actual results:
The schemaLocation attribute of an imported XSD looks like:

Expected results:
The schemaLocation attribute should be like:

Note You need to log in before you can comment on or make changes to this bug.