function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
ChellappaChellappa 

WSDL Conversion to Apex Issue with Schema definitions

Hi ,

 

I am finding a strange issue with the generated Apex code from the WSDL file.

 

<?xml version="1.0" encoding="UTF-8"?>

<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<env:Header/>

<env:Body>

<CustomerTnC_Input xmlns="http://ycrm.yahoo.com/schemas/CustomerSchema/SelfServe">

<ListOfYmitSsContact>

<Contact xmlns="http://www.siebel.com/xml/YMIT%20SS%20Contact">

<ContactSiebelId>1-94JH6X</ContactSiebelId>

<YMITSSTCTimestamp>05/05/2011 12:12:12</YMITSSTCTimestamp>

<YMITSSUserId></YMITSSUserId>

</Contact>

</ListOfYmitSsContact>

</CustomerTnC_Input>

</env:Body></env:Envelope>

 

This is the request XML generated to the WS call.. 

If you look at the highlighted portion above, it doesnt have any XMLNS attached to it. So it inherits the namespace of its parent tag.

 

But according to the WSDL it should have a namespace similar to the one below it.

 

Hence there is a validation issue with the TIBCO side and they are sending fault response.

 

In the WSDL everything seems to be properly placed. I am not able to figure out how the Namespace is missing for the highlighted element.

 

Any clue to this would be of great help.As we are at the end of development, help would be greatly appreciated.

 

i Can post the WSDL if required.

 

Thanks in advance.,

Chellappa