Last updated on MAY 25, 2016
Applies to:Oracle JDeveloper - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
While working with Web Services in an Eclipse development environment and having an extensive library of XSD schemas and WSDLs that are used as the canonical model, there is a need to reuse this model in JDeveloper as well but there is not a good way to keep the library structure with relative paths so that one source can be used by both, Eclipse and JDeveloper.
These XSD and WSDL files are located in multiple projects which reference each other. For example, there is a customer library project that contains the customer object which references another library project, the common library, which contains an Address object. Customer -> Address
In Eclipse, a project reference is setup to allow one project to be able to reference the other using relative paths.
The Customer XSD, contains an import to the other xsd for reference because it contains an element of type Address.
Notice, the relative reference does not include the name of the Common Library because the files in this library are available to the Customer Library via project reference.
When trying to use these library projects in JDeveloper, the relative paths don't resolve to the files and even trying to add project dependencies (via Project / Properties / Dependencies) to achieve this, unfortunately this doesn't work. The only way to make it work was to update the relative paths in the import statement by extending the relative path to go up higher in the directory structure and back down, using the Common Library name in the path.
The question is how to achieve the above desired functionality so that it is possible to work with both JDeveloper and Eclipse at the same time?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms