|
Did you update your PTF's etc as mentioned in the link.Yes, I did
client ... because we can't (or don't want) to change the client (an old
Maybe this might help.
https://stackoverflow.com/questions/24224226/how-to-fix-soapenvenvelope-issue-in-xsd-schema-while-validating-with-soap-reque
I don't understand if I have to change something in my WSDL or in the
On Thu, Apr 8, 2021 at 12:45 AM Roberto De Pedrini <
roberto.faq400@xxxxxxxxx>
wrote:
Hi all from Italy,https://www.ibm.com/support/pages/how-migrate-your-ibm-integrated-web-services-iws-server-v13v15-v26
I'm trying to help one of my customer to migrate some SOAP web services
from an IWS 1.5 (on a 7.2 partition) to an IWS 2.6 (on a 7.3 partition).
Following those IBM documents (
and https://www.ibm.com/support/pages/node/1138636) it seems all OK:redeploying
1 Save WS from IWS 1.5 with saveWebServices.sh
2 Restore WS to IWS 2.6 with restoreWebServices.sh
3 Add rewrite rules on HTTP.CONF and restart the server
4 Test the old client (SOAPui for me) changing only endpoints
5 It works! All ok, no other modification to my old client
But if I stop my web service on IWS 2.6 (7.3), and try only to
it without any changes, something change in the WSDL and I got"Unexpected
wrapper element .../xsd" message from SOAPui "call"list
soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<soap:Fault>
<faultcode>soap:Client</faultcode>
<faultstring>Unexpected wrapper element {
http://wspub02.wsbeans.iseries/xsd}dipendenti_list found. Expected {
http://wspub02.wsbeans.iseries}dipendenti_list.</faultstring>
</soap:Fault>
</soap:Body>
</soap:Envelope>
wspub02 is my WebService
dipendenti_list is one of the methods (procedures)
Why I can migrate but not redeploying services? Or
Thanks
--
--
Roberto De Pedrini - Faq400 Srl
http://blog.faq400.com/en
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx--
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.