Soap Header Exception while adding new function

We added one new functionality in the server . We changed the wsdl file and also in the service_v4.php and when updated the web reference the changes got reflected and also the new reference.cs is generated.But when we call that function an exception is thrown as “function does not exist”.

<definitions xmlns:SOAP-ENV="" xmlns:xsd="" xmlns:xsi="" xmlns:SOAP-ENC="" xmlns:tns="urn:xmds" xmlns:soap="" xmlns:wsdl="" xmlns="" targetNamespace="urn:xmds">
    <xsd:schema targetNamespace="urn:xmds">
        <xsd:import namespace="" />
        <xsd:import namespace="" />
            <message name="GetVolumeRequest">
    <part name="serverKey" type="xsd:string" />
                            <part name="displayName" type="xsd:string" />
            <message name="GetVolumeResponse">
                            <part name="volume" type="xsd:int" />

<portType name="xmdsPortType">
                            <operation name="GetVolume">
        <documentation>Getting the volume of the display</documentation>
        <input message="tns:GetVolumeRequest"/>
        <output message="tns:GetVolumeResponse"/>
<binding name="xmdsBinding" type="tns:xmdsPortType">
    <soap:binding style="rpc" transport=""/>
                            <operation name="GetVolume">
        <soap:operation soapAction="urn:xmds#GetVolume" style="rpc"/>
            <soap:body use="encoded" namespace="urn:xmds" encodingStyle=""/>
            <soap:body use="encoded" namespace="urn:xmds" encodingStyle=""/>
<service name="xmds">
    <port name="xmdsPort" binding="tns:xmdsBinding">
        <soap:address location="{{XMDS_LOCATION}}"/>

Check your web server’s temporary file location. It generates a cache for the webservice which you may need to delete to get your new functionality working.

With regard to getting that code included in to the main Xibo codebase (which is something we’d really like to do), we’d need you to complete a specification etc for this before making changes so we can discuss with you the best way to implement it (perhaps without needing to add webservice calls). Dan gave you the information you need to do that over on your other thread:

Best wishes


I definitely don’t think we want to implement this with another web service call - this information should be sent to the players with all of their other settings as mentioned in the other thread (the original one you started and the one that Alex linked back to).

We shouldn’t add duplicate web service calls unnecessarily as they increase the bandwidth and load on the CMS. Plus the fact, it would be far easier to have these settings “come down” with the normal settings.

Thank you Dan and Alex,

We will try to do with the other basic settings. As we are newbies for this, could you please elaborate on normal settings?

The place to have the discussion about how to implement this is over in your Feature thread: