The client stubs generated from the Web services must be installed in various other front-end applications that communicate with the Oracle Endeca Server. When you upgrade the Oracle Endeca Server, to ensure compatibility with the newer versions of the interfaces, regenerate the client stubs.
To resolve incompatibility of Web service versions and client stubs:
This is typically done as part of an upgrade to the Oracle Endeca Server software.
Read the Migration Guide for the upgraded version of the Oracle Endeca Server to learn about changes to the Web service interfaces.
When the stubs are compiled, the new version of the interface is read from the Web service's WSDL.
If the import statement in the client code using stubs generated from an unversioned web service looked similar to this example:
import com.endeca.www.mdex.transaction._2011.startOuterTransactionDocument;
change the import statement to indicate the versions:
import com.endeca.www.mdex.transaction._2._0.startOuterTransactionDocument;
The namespaces for each operation indicate which versions are supported for this operation. In this case, the startOuterTransaction operation is supported in version 2.0.