All,

This maybe OT for this group, but I am really after some views on our issue,
with Acrobat Elements server 6.0 the webservices work fine, with 6.0.1 they
don't, this is the XML that comes back :

<?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-72fce16e2912</jobID>
 </namesp1:createPDFResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

The problem is in the 3 parameters: status, errorMessage and jobID. They
should strictly have the "urn:aaes" namespace, as their parent element
createPDFResponse. However, because the namespace is defined as a prefix,
rather than the default namespace, it is not carried to the child elements,
so they are not recognised.

Is the above statement correct? or should .NET be forgiving?

Cheers

Steve