Here’s one I didn’t see before. When you create XML Schemas, or WSDL artifacts in JDeveloper, and use the MDS for importing XSDs or WSDLs, you might encounter a JDeveloper error at the oramd- statement saying “referred schema is outside the current project context”.
When you have a SOA Tier project, and you create for example a WSDL using the wizard, the default location it is stored is “<project folder>/public_html/WEB-INF/wsdl. In JDeveloper, it is then placed under Web Content.
If you edit your WSDL here, and use the oramds:/ directive, you’ll get the mentioned error, even when the oramds:/ URI is correct and the MDS is set up correctly in the Application.
However, if you do the same in a WSDL within the “SOA Content” folder, it does work, as shown in WSDLDocument2.wsdl in the picture below.
So apparently the “project context” of the MDS within a JDeveloper SOA Tier project is the “SOA Content” folder. Okay, I didn’t know that. I want a hour of my life back!oramds versus "referred schema is outside the current project context",