MDS-00013 Error From MDS Mentions Taskflow that does not Exist in Application
(Doc ID 2537792.1)
Last updated on APRIL 12, 2022
Applies to:
Oracle JDeveloper - Version 11.1.1.9.0 and laterInformation in this document applies to any platform.
Goal
On an ADF 11.1.1.9.0 application, MDS error is seen while working with it in the standalone WLS server: MDS-00013 "no metadata found for metadata object" error from MDS
Error Log:
Caused by: oracle.mds.core.MetadataNotFoundException: MDS-00013: no metadata found for metadata object "/WEB-INF/<TASK-FLOW-DEFINITION>.xml"
MDS-00201: PDocument not found in MetadataStore : [store-type=DefaultMetadataStore app-name=<APPLICATION> lookup-order=ServletContext,Classpath]
at oracle.mds.core.MetadataObject.getBaseMO(MetadataObject.java:1598)
at oracle.mds.core.MDSSession.getBaseMO(MDSSession.java:4200)
at oracle.mds.core.MDSSession.getMetadataObject(MDSSession.java:1726)
at oracle.mds.core.MOResolver.getMetadataObjects(MOResolver.java:245)
at oracle.adfinternal.controller.metadata.provider.mds.MdsMetadataResourceProvider.getMetadataObjects(MdsMetadataResourceProvider.java:452)
Customer claimed the task flow object shown in the message included in the application code but still MDS complains about the file reference.
Solution
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
Goal |
Solution |