Imported XSD Files are Still Cached after Redeploying the BPEL Process
Last updated on JUNE 18, 2018
Applies to:Oracle(R) BPEL Process Manager - Version: 10.1.3.1 to 10.1.3.4 - Release: AS10gR3 to AS10gR3
Information in this document applies to any platform.
***Checked for relevance on 21-Apr-2010***
There are two or more BPEL processes and one of the processes used a XSD of another process. If there is a change in the XSD of the second process, like for example changing the type inside the XSD, the first process still caches the old version of the XSD, although the first process is redeployed after changing the XSD.
The only workaround is to restart the server. Deploying the first and the second process without restarting the server doesn't help.
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