WSDL-to-Java Conversion Error (Doc ID 1633114.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle SOA Suite - Version 11.1.1.7.0 and later
Information in this document applies to any platform.

Goal

customer getting a WSDL-to-Java conversion error when wiring a Spring component with a WebService :

Wsdl-to-Java conversion of FARICheckOut.wsdl returned errors :
Error creating model from wsdl "file:/C:/Works/WS_JDEV/TestProjects/FARICheckOut.wsdl" :
a class/interface with the same name "java.ch_post_it_fari_bindings_checkout.Staging" is already in use.
Use a class customization to resolve this conflict.
...

The WSDL file contains two schemas in two different Namespaces:
java:ch.post.it.fari.bindings.checkout.req
java:ch.post.it.fari.bindings.checkout.res

Both schemas contain elements with the same name.
It seems that the .req and .res are ignored and only java:ch.post.it.fari.bindings.checkout is considered to create the package-name.
Therefore a naming conflict occurs.

Is it possible to use the complete namespace (include .res or .req)?
How to use a class customization?

How should this be handle in this case?

And final comment:
Customer can't change the namespaces (the Web Service doesn't belong to the customer).
 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms