Web Service Manager Does Not Recognize Custom Opcode and Throws Error "java.lang.Exception: Converting opcode name "MY_OP_CUST_CREATE_DEPOSIT" to opcode number" (Doc ID 2116178.1)

Last updated on MAY 20, 2022

Applies to:

Oracle Communications Billing and Revenue Management - Version 7.5.0.13.0 to 7.5.0.22.0 [Release 7.5.0]
Information in this document applies to any platform.

Goal

Scenario:

One user has deployed custom opcode as per this documentation: Creating a Custom Web Service. But Web Service Manager does not recognize custom opcode and not able to call opcode from other Simple Object Access Protocol (SOAP) clients.

Errors:

Note: When the same is executed with opcode number instead of opcode name, it goes through fine.

How to resolve this issue?

Solution

	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

Goal

Solution

References

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

Web Service Manager Does Not Recognize Custom Opcode and Throws Error "java.lang.Exception: Converting opcode name "MY_OP_CUST_CREATE_DEPOSIT" to opcode number" (Doc ID 2116178.1)

Applies to:

Goal

Solution

To view full details, sign in with your My Oracle Support account.

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