Subject:Web Service Author:J D Date:03 Sep 2007 04:59 AM
When building a web service call in Stylus Studio, I am unable to use the edit window above the SOAP request to modify the "Value". I can type in the field, but the value is canceled when I click to the next field and the SOAP request is not changed. If I edit the request manually, it launches fine, but no results.
It's for a local web service that a vendor supplies.
Their tool allows me to connect and issue the soap request and get results, but I cannot do the same with Stylus Studio
Subject:Web Service Author:J D Date:03 Sep 2007 08:34 AM
Let me add the following.
1) If I edit the soap request slightly by removing the first namespace after <tns:GetObjectContent ... then I am able to edit the WSDL Values... Interesting?
Here's the changed SOAP request that I can now edit (but this is not what Stylus Studio produces when it examines the WSDL (attached below also)
Subject:Web Service Author:J D Date:03 Sep 2007 05:46 PM
Ok, so I tried out the option Stylus Studio has to convert the SOAP request into an xquery. It does the conversion and I get results. It creates a bunch of namespaces and I've stripped them all away (unnecessary). Still good results. Here's what I have:
So, I went back at the SOAP request (I need it to be embeded in a small demo app). I simplified it down to this, which generates as close as I've come to the same XQuery above (still works, just like the original - same results via XQuery). So, why does the SOAP request not give me any results when run in Stylus Studio? How is it possible to take a bad SOAP request and automatically turn it into a good XQuery?
Any ideas on why that SOAP request is bad and how I can fix it? Since the XQuery works, this is not a vendor problem with the WSDL, is it? Perhaps an issue with Stylus Studio?
Subject:Web Service Author:J D Date:04 Sep 2007 03:31 AM
Ok, so I tried out the option Stylus Studio has to convert the SOAP request into an xquery. It does the conversion and I get results. It creates a bunch of namespaces and I've stripped them all away (unnecessary). Still good results. Here's what I have:
So, I went back at the SOAP request (I need it to be embeded in a small demo app). I simplified it down to this, which generates as close as I've come to the same XQuery above (still works, just like the original - same results via XQuery). So, why does the SOAP request not give me any results when run in Stylus Studio? How is it possible to take a bad SOAP request and automatically turn it into a good XQuery?
Any ideas on why that SOAP request is bad and how I can fix it? Since the XQuery works, this is not a vendor problem with the WSDL, is it? Perhaps an issue with Stylus Studio?
Subject:Web Service Author:J D Date:05 Sep 2007 06:27 AM
The output window is always blank.
The reason for the change in IP address is because I was attempting it locally when I started, and now I have it running in a virtual machine.
The issues remain
1) Stylus Studio (and the Oxygen product also by the way) cannot give me any results for the SOAP request
2) Stylus Studio does not allow me to type values into this particular web request, but allows me to do so for others.
My point was to build/troubleshoot a web request that I was creating in Adobe Flex 2. I have found another product called Charles that helped me solve my problem with Flex and the SOAP request there is now working fine. Seems to me there are just a couple of bugs in Stylus Studio and perhaps some other XML editing tools like Oxygen.
It would be nice to confirm, but I'm very certain the inability to type in the value cells is a problem with the parsing of the namespaces. As for not returning any results, I do not know. I can't seem to find a way to trace the communication of stylus studio to offer any more details of the problem...
Please help when you have a chance. It would be nice to use this tool to check web service results quickly.
Subject:Web Service Author:J D Date:06 Sep 2007 06:00 AM
Thank you very much.
If you can send me a personal email, I will let you know along with a live (external) web address where you can connect to the WSDL as soon as I can get somebody to set it up.
Best Regards and thanks for your time and assistance!
Subject:Web Service Author:Ivan Pedruzzi Date:26 Sep 2007 05:27 PM
The issue has been solved off-line.
It turned out that this particular Web Service implementation doesn't like SOAP requests indented. Removing all ignorable white-space solved the problem.