SOA 11g: Failed to Read WSDL Imports when Using Relative Paths
(Doc ID 1571646.1)
Last updated on JUNE 18, 2018
Applies to:Oracle SOA Platform - Version 126.96.36.199.0 and later
Information in this document applies to any platform.
If Service WSDL imports a fault WSDL which itself imports a schema file defining the fault payload - and the imports are using relative paths -
- BPEL processes will fail when initializing BPEL variables (type not found).
- Services cannot be tested in EM
- Resource access through http (e.g. soapUI or through Web browser) doesn't work
This behaviour is encountered inPS6, i.e. 188.8.131.52.
Version 184.108.40.206.0 (PS5) only showed resource errors during startup, but could still be run.
At design time everything works; i.e. Files are resolvable and validated.
At runtime the relative paths from the 2nd import are not resolved correctly. The fault-WSDL is correctly resolved from the service-WSDL, however the schema file imported within the fault-WSDL cannot be located.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document