Error deploying Oracle Composite with wrong encoding wsdl

We had some issues with deploying a composite which retrieves his wsdl for the partnerlinks from Nexus.
The supplier of the services adds the archive with the wsdl artifacts in Nexus, we download the dependency and after that we compile/validate the composite against the downloaded set of artifacts.

For one particular partnerlink the composite just wouldn’t compile.

Error message :

[code language=”xml”]
Validating composite “c:\Repos\composites\mydomainobject\MyService\composite.xml”
c:\Repos\composites\mydomainobject\MyService\composite.xml:21: error: Load of wsdl “oramds:/apps/xsd/nextgen/gm/services/mydomainobject/2/myservice.wsdl” failed
c:\Repos\composites\mydomainobject\MyService\composite.xml:44: error: Cannot find Port Type “{http://ibx.nl/gm/services/mydomainboject/2}MyServicePortType” for “Service1” in WSDL Manager
c:\Repos\composites\mydomainobject\MyService\composite.xml:44: warning: Failed to Find Binding “Service1″:”{http://ibx.nl/gm/services/mydomainboject/2}MyServicePortType” in WSDL Manager
c:\Repos\composites\mydomainobject\MyService\composite.xml:44: warning: Failed to Find Binding “Service1″:”{http://ibx.nl/gm/services/mydomainboject/2}MyServicePortType” in WSDL Manager
c:\Repos\composites\mydomainobject\MyService\composite.xml:30: error: Cannot find Port Type “{http://ibx.nl/gm/services/mydomainboject/2}MyServicePortType” for “Service1” in WSDL Manager
c:\Repos\composites\mydomainobject\MyService\composite.xml:63: error: Cannot find Port Type “{http://ibx.nl/gm/services/mydomainboject/2}MyServicePortType” for “Mediator” in WSDL Manager
c:\Repos\composites\mydomainobject\MyService\composite.xml:63: error: Cannot find Port Type “{http://ibx.nl/gm/services/mydomainboject/2}MyServicePortType” for “Service1” in WSDL Manager
[/code]

After recreating the partnerlink over and over again we thought the wsdl for it just looked valid. After selecting the wsdl when we create the partnerlink it also parses the operations correctly, so it looks valid.
The error message is a bit misleading.

Eventually we noticed the encoding of the wsdl itself was changed from ANSI to UTF-8.

Change the encoding back to ANSI (Notepad++), refresh mds, recreate the partnerlink and compile the composite and we have one happy composite again.

Share this Post:
Digg Google Bookmarks reddit Mixx StumbleUpon Technorati Yahoo! Buzz DesignFloat Delicious BlinkList Furl

Comments are closed.