FW: SOAP Response Messages For Business Adaptor Based Services Cannot Be Parsed
(Doc ID 783124.1)
Last updated on AUGUST 24, 2020
Applies to:Oracle Utilities Framework - Version 2.1.0 to 18.104.22.168.0 [Release 2.1 to 2.2]
Information in this document applies to any platform.
When using the WSDL generated for a web-enabled Business Object or Business Service with Axis 1.4
to generate web service client code (proxy code), the resulting response message cannot be
parsed. A SAXException occurs when the message is processed by the Axis framework.
Took the generated WSDL and using axis 1.4, generated a web service client. Created some
test code that used the generated web service proxy code to call the web service. When running the
code, the request and response is in a sniffer (attached as request-response.txt), so the call is being made to XAI and getting serviced; however, when axis tries to deserialize
the response, there is an exception (attached as exception.txt). By comparing the response from a
web-enabled business adapter type service with one of the web-enabled services done through
SchemaEditor, the problem is that the top-level element in a business adapter based
service is not namespace qualified.
-- Steps To Reproduce:
Create a new Java EE web application in Eclipse (I used 3.4.1). Create a new web service client
based on the WSDL for a web-enabled Business Object or Business Service generated by the CC&B
2.2.0 framework. Create a test program that uses the generated proxy code to call the web-enabled
service. When the response is returned, a SAXException will be thrown when parsing the message.
This problem is important since no implementation can use XAI Business Adaptor on FW 2.1.
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