Changes to an XSL File Stored in MDS (oramds:/apps) does not get Reflected in a Process Composite Using the XSLT
(Doc ID 1268478.1)
Last updated on JANUARY 04, 2021
Applies to:Oracle SOA Suite - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
You have stored SOA XSL artifacts in MDS following this documentation:
Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite 11g Release 1 (11.1.1)
Part Number E10224-05
Section 41.7.3 Deploying and Using Shared Metadata Across SOA Composite Applications in Oracle JDeveloper
This will place the XSL artifacts under the oramds:/apps structure in MDS. For example into:
In SOA 126.96.36.199.0, changes to these XSL MDS artifacts are not picked up by the composite processes that reference them until the referencing process is re-deployed or the SOA Managed server is restarted or the composite state is changed from "Activate" to "Retire" and then back to "Activate".
The following example illustrates the problem:
- Create a MDS Shared Metadata JAR file which contains a XSL with mapping:
- Add the above archive as part of a SOA Bundle for a composite called XSLTestComposite
- Change the transform in XSLTestComposite's .bpel file to oramds:/apps/TestXSLTransform.xsl [a MDS location]
- Change the transform in XSLRefererComposite's .bpel file to oramds:/apps/TestXSLTransform.xsl [a MDS location]. XSLRefererComposite is a separate (separate from the SOA Bundle) deployment that refers to the XSL stored in the MDS
- Deploy the SOA Bundle
- Deploy the XSLRefererComposite
- Test both cases: Observe that the result is 1->5, 2->4, 3->3, 4->2, 5->1 (this is correct)
- Change the XSL (of the MDS Shared Metadata) to 1->1, 2->2, 3->3, 4->4, 5->5 and redeploy the SOA Bundle
- Test both cases: Observe that the result is:
1->1, 2->2, 3->3, 4->4, 5->5 for XSLTestComposite (as it has been redeployed as part of SOA Bundle, it is correct)
1->5, 2->4, 3->3 ,4->2, 5->1 for XSLRefererComposite. (this is not correct, it should be 1->1, 2->2, 3->3, 4->4, 5->5, i.e. the XSL mapping change was not picked up).
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