×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Hi, There is no way to get around this. The endpoint you can probably get
around by using HTTP URL mappings documented on page 131 of the
administration and programming guide [1]. The namespace cannot be
resolved. You will have to send your clients the new WSDL.
[1]
https://www.ibm.com/systems/power/software/i/iws
----- Original message -----
From: Eric <send2et@xxxxxxxxx>
Sent by: "WEB400" <web400-bounces@xxxxxxxxxxxx>
To: "Web Enabling the IBM i (AS/400 and iSeries)" <web400@xxxxxxxxxxxx>
Cc:
Subject: [WEB400] Namespace on IWS v2.6
Date: Tue, May 23, 2017 4:24 AM
Hi,
Our client has upgraded from V7R1 to V7R3 and we noticed a few issues with
the IAS and IWS.
Eg. IAS is no longer supporting v8.1 and no longer supporting Java 6.
I also noticed that IWS v1.5 no longer exist. It's v2.6 now.
I've tried recreating the server / service.
After everything is done, I noticed that the XML structure generated by
the
WSDL is different.
The end point is also different because it's using a different framework
which is faster.
Some namespace are no longer there and some has changed.
We are trying to minimise the impact to the other vendors which have to
call the web service.
Does anyone know whether it would be possible to change the namespace so
that we make it the same as what it was before when it was running on
v1.5?
This means only the endpoint which is changed.
Thanks,
Eric
midrange.com
