|
| 6.0.1 Invalid Soap Response |
 |
Fri, 27 Jan 2006 04:44:03 -070 |
After developing integration with Adobe Elements 6.0.0 web services then finding
Adobe had altered their interface for 6.0.1 (see an earlier post), we've tried
modifying our .Net application to work with this new soap service. However,
Microsoft Soap technologies cannot handle the response. This is because the
response is invalidly generated by Adobe Elements Server - not an issue with the
Microsoft technologies.
I expect, like my previous posting, this will be totally ignored by Adobe.
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance"
xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/1999/XMLSchema"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<SOAP-ENV:Body>
<namesp1:createPDFResponse xmlns:namesp1="urn:aaes">
<status xsi:type="xsd:int">0</status>
<errorMessage xsi:type="xsd:string"/>
<jobID.xsi:type="xsd:string">4dfba64e-a8bd-4bb9-a274-72fce16e291
2</jobID>
</namesp1:createPDFResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
|
| Post Reply
|
| Re: 6.0.1 Invalid Soap Response |
 |
Thu, 2 Feb 2006 07:00:02 -0700 |
|
| Post Reply
|
| Re: 6.0.1 Invalid Soap Response |
 |
Thu, 2 Feb 2006 07:00:02 -0700 |
|
| Post Reply
|
|
|
|
|
|
|
|
|
|