WLS 10.3.3 - Client got null values from the response
(Doc ID 1309418.1)
Last updated on OCTOBER 13, 2020
Applies to:Oracle WebLogic Server - Version 10.3.3 to 10.3.3
Information in this document applies to any platform.
In WLS 10.3.3- User-defined types are NOT parsed correctly in JAX-RPC web services using the RPC/ENCODED SOAPBinding.
The web service client code generates requests that do not include the java: namespace, so user-defined types are not parsed correctly.
Deploy <AppName>.ear using the weblogic console.
Then check for Service Request and Service Response for ComplexRPCImpl web service entry.
Below is the output of a RPC/ENCODED SOAP Request generated in WLS 10.3.3
The expected result would be to have the StringValue in the response
equal to 'string' and the intValue equal to 3.All the values in the client code comes as null.
Modifying the request to include the java: namespace in front of each of the values causes the proper response to be generated.[i.e <java:IntValue>3</IntValue>]
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