WebLogic Web Services XSD Relative Location Not Preserved (Doc ID 1351859.1)

Last updated on JUNE 09, 2016

Applies to:

Oracle Weblogic Server - Version 11.1.1.1.0 to 11.1.1.5.0 [Release 11g]
Information in this document applies to any platform.

Symptoms

After creating a web service with an xsd import ( relative location ) such as

<xsd:import schemaLocation="./xsd/address.xsd"

 
and then deploying the WAR to WebLogic server 10.3.x the WSDL is checked in the WLS admin console.

The console shows the WSDL location with something like:

<xsd:schema targetNamespace="http://test.net/types"
elementFormDefault="qualified">
<xsd:import
schemaLocation="http://localhost:7001/testws/ContactPort?xsd=1"
namespace="http://test.net"/>
</xsd:schema>


The deployment WAR specifies a relative location, but once deployed to the WebLogic server this
is replaced by the actual host:port URL of the server. Why is the relative location not preserved?



Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms