My Oracle Support Banner

SOA 10g: Cannot Register ESB Artifacts Using JDEVELOPER if Workspace Name is Changed (Doc ID 875558.1)

Last updated on MAY 15, 2023

Applies to:

Oracle Enterprise Service Bus - Version to
Information in this document applies to any platform.


When an ESB project is registered using JDeveloper and then moved to a new JDEV Workspace with a different Workspace name, re-registration of the ESB project and its related artifacts (XSL Stylesheets, XML Schemas, WSDL files) might fail.  When the failure occurs, if you have <Patch 8627696> installed JDeveloper will not display the ESB services confirmation window and you will find in:


the following entries which will notify you, that the artifacts will be ignored during deployment.

<MSG_TEXT>In deployment, Ignore esb service with WSDL URL = esb:///ESB_Projects/Misc_Tests_TestESBRegistration/FileIn.wsdl</MSG_TEXT>
<MSG_TEXT> xml returned :&lt;deploymentSummary>
&lt;message>Entity Deployment Failed&lt;/message>

You get the same registration failure without <patch 8627696> installed but a different error is given in log.xml:

WSDL "esb:///ESB_Projects/Misc_Tests_TestESBRegistration/FileOut.wsdl" of service "DefaultSystem.FileOut" is invalid or unaccessible. Following error is thrown by WSDL Parser : WSDL Parsing Failed: org.apache.slide.structure.ObjectNotFoundException: No object found at /files/ESB_Projects/Misc_Tests_TestESBRegistration




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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.