MDS Cache not Updated after WSDL Change
Last updated on JANUARY 24, 2018
Applies to:Oracle SOA Suite - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
On : 18.104.22.168.0 version, Deployment
SOA/ MDS caching issue
After updating the MetaData Services' (MDS) WSDL endpoint, it's noticed that previous endpoint was being used.
Even after you redeployed the WSDL the change is not effective, and previous endpoint is used.
Steps To Reproduce:
The issue can be reproduced at will with the following steps:
1. Change WSDL endpoint in MDS store
2. The composite fails to execute trying to use old endpoint
(any WSDL change is not effective)
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