XML Editor
Sign up for a WebBoard account Sign Up Keyword Search Search More Options... Options
Chat Rooms Chat Help Help News News Log in to WebBoard Log in Not Logged in
Show tree view Topic
Topic Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Go to previous topicPrev TopicGo to next topicNext Topic
Postnext
Rick CavallaSubject: Web Service Call
Author: Rick Cavalla
Date: 24 Apr 2006 08:02 PM
Originally Posted: 24 Apr 2006 04:40 PM
Hello,<br> I am using Stylus' Web Service Call feature. However, the recipient of the call cannot parse the resulting XML. They have been using a product called XML Spy to generate the XML for their internal testing. The XML generated from XML Spy is quite a bit different than that generated by Stylus Studio. Can you explain why the same WSDL would generate different web service call XML? Is there an option somewhere that can toggle between different styles of SOAP/XML?<br> <br> Thank you,<br> Rick Cavalla<br> Enable Corporation<br>


DocumentECOM_to_AES_SalesOrderGetStat.wsdl
WSDL

DocumentRequest_Stylus.xml
SOAP Request from Stylus

DocumentRequest_XMLSpy.xml
SOAP Request from XML Spy

Postnext
Minollo I.Subject: Web Service Call
Author: Minollo I.
Date: 24 Apr 2006 04:47 PM
Rick,
can you attach the WSDL file, and the SOAP request you would expect?

Thanks,
Minollo

Postnext
Rick CavallaSubject: Web Service Call
Author: Rick Cavalla
Date: 24 Apr 2006 08:04 PM
Originally Posted: 24 Apr 2006 07:55 PM
Minolla,<br> I have attached the documents to my original message. I had no expectations about the SOAP Request, per se. I just take Stylus' word for it. :-)<br> <br> Thanks, Rick<br>

Postnext
Rick CavallaSubject: Web Service Call
Author: Rick Cavalla
Date: 24 Apr 2006 08:07 PM
What is with all the <br>'s when you edit your own message? It turns all the carriage returns into <br> and I cannot find a way to undo it. Sorry about that.

-Rick

Postnext
Tony LavinioSubject: Web Service Call
Author: Tony Lavinio
Date: 24 Apr 2006 09:34 PM
The <BR>'s are an artifact of the old message board software
that we've been using; we are in the process of updating it.

Postnext
Ivan PedruzziSubject: Web Service Call
Author: Ivan Pedruzzi
Date: 25 Apr 2006 10:22 AM
Hi Rick

Thank You for the test case we are investigating.

Ivan Pedruzzi
Stylus Studio Team

Postnext
Rick CavallaSubject: Web Service Call
Author: Rick Cavalla
Date: 27 Apr 2006 10:18 AM
Guys,
Any updates on this? If we do not receive feedback soon, our partner wants us to switch to XML Spy. We use OpenEdge and SonicMQ, so we would like to "keep it in the family" and use Stylus Studio. However, our partner is footing the bill for this project, so we are not calling the shots.

Thanks,
Rick

Postnext
Ivan PedruzziSubject: Web Service Call
Author: Ivan Pedruzzi
Date: 27 Apr 2006 11:37 AM
Rick,

We discovered a defect when dealing with RPC literal and fixed it.
We are planning to ship a Stylus Studio update in a week or so, as soon as QA passes.

Hope this help
Ivan Pedruzzi
Stylus Studio Team

Postnext
Rick CavallaSubject: Web Service Call
Author: Rick Cavalla
Date: 19 Jun 2006 12:46 PM
I am still having issues getting this WSDL to generate the correct XML. When I feed it into Stylus, the first line is:

<SOAP-ENV:Envelope xmlns="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">

That is rejected when we call the web service. Plus, I cannot enter attribute values in the Name/Type/Value browser that appears above the XML.

I have been able to solve both problems by manually changing the first line to:

<SOAP-ENV:Envelope xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">

That ":SOAP-ENC" seems to make all the difference. Obviously, though, it is a pain to enter that by hand for every call. I also worry that there may be other errors I am not seeing. Can you look into this?

Thanks,
Rick Cavalla

Posttop
Ivan PedruzziSubject: Web Service Call
Author: Ivan Pedruzzi
Date: 19 Jun 2006 01:41 PM
Hi Rick,

The problem you are experiencing is caused by the missing soap-encoding declaration in the WSDL root, a condition that Stylus Studio currently handles improperly.

If you can edit the WSDL (or work with a local copy) please change the root to

<wsdl:definitions
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:jms="http://schemas.xmlsoap.org/wsdl/jms/"
xmlns:mns="ECOM_ECOM_to_AES_SalesOrderGetStat"
xmlns:ns1="http://abtapwbi001:8095/GetStat"
xmlns:ns2="http://abtapwbi001:8095/WBIDEV/ECOM"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="ECOM_ECOM_to_AES_SalesOrderGetStat-interface"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="ECOM_ECOM_to_AES_SalesOrderGetStat-interface"
name="ECOM_to_AES_SalesOrderGetStatService-interface">


The behavior will be corrected in the next update.

Thank You for your help
Ivan Pedruzzi
Stylus Studio Team

 
Topic Page 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 Go to previous topicPrev TopicGo to next topicNext Topic
Download A Free Trial of Stylus Studio 6 XML Professional Edition Today! Powered by Stylus Studio, the world's leading XML IDE for XML, XSLT, XQuery, XML Schema, DTD, XPath, WSDL, XHTML, SQL/XML, and XML Mapping!  
go

Log In Options

Site Map | Privacy Policy | Terms of Use | Trademarks
Stylus Scoop XML Newsletter:
W3C Member
Stylus Studio® and DataDirect XQuery ™are from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2016 All Rights Reserved.