massimo__croci wrote:Same issue of this post?

https://www.devconnectprogram.com/forums/posts/list/24939.page#p163829

It is similar.

In my case, I can only import AEP 8.1.1 WSDL file by AAOD axis2.
If I import it by other ways, the WSDL file can not be used.

Hi,

In AEP 8.1.1, I use IVR speech applications to invoke a restful application, which is on the IIS.
The restful application return a xml result, and IVR speech application can receive it by the web service operation(REST).

When I show the complete result, it works fine.
However, if we parse the result with XPath, non-ASCII characters become garbled.

The attachments are simple applications, which invoke a xml file by the web service operation(REST).
It will write logs after invoking a xml file, and non-ASCII characters can NOT be shown correctly when using XPath in AAOD 8.1.1 .

This issue happens when we export applications by AAOD 8.1.1,
but does NOT happen when we export applications by AAOD 7.0.1 .

If I use avrest-rt-07.01.08.04.jar from AAOD 7.0.1, rename it to avrest-rt-08.11.08.01.jar,
and put it into AAOD 8.1.1 speech to replace the original file, it can work fine, too.

Hi,

In C# project, I add a web reference, and input the WSDL address of “Application Interface Web Service”.
But some error occurr, the C# project can not create codes from the xml document of “Application Interface Web Service”.

It works when I add AAOD 6 or AAOD 7.2 WSDL document into web references in the same way.

I try to test AAOD 8.1.1 WSDL document in other ways,
it only can be used by apache axis 2, and can not be used by .Net or apache axis 1.4

I try to verify the WSDL document in https://www.wsdl-analyzer.com/
The documents from AAOD 6 and AAOD 7.2 passed, but the document from AAOD 8.1.1 failed.

The attachment contains my C# test project, and WSDL files from AAOD 6, AAOD 7.2, AAOD 8.1.1