Input Message of Operation 'buscarContrato'

Differences:

Input Template

The message templates below show how an original message and a message based on the modified WSDL will look like.

Original Modified 
<ns1:buscarContrato xmlns:ns1='cadastro.beg.tfs.totvs.com'>
<!-- optional -->
  <contrato>?999?</contrato>
<!-- optional -->
  <sincronizarBases>?true?</sincronizarBases>
</ns1:buscarContrato>
 
<ns1:buscarContrato xmlns:ns1='cadastro.beg.tfs.totvs.com'>
<!-- optional -->
  <contrato>?999?</contrato>
<!-- optional -->
  <sincronizarBases>?true?</sincronizarBases>
<!-- optional -->
  <forcarSincronizacao>?true?</forcarSincronizacao>
</ns1:buscarContrato>

Schema Definition

The following schemas are only showing definitions that are relevant to the message. The real schemas might be bigger.

Original Modified 
<xsd:schema targetNamespace='cadastro.beg.tfs.totvs.com' attributeFormDefault='unqualified' elementFormDefault='unqualified' xmlns:xsd='http://www.w3.org/2001/XMLSchema' xmlns:tns='cadastro.beg.tfs.totvs.com'>
  <xsd:element name='buscarContrato' type='tns:buscarContrato' />
  <xsd:complexType name='buscarContrato'>
    <xsd:sequence minOccurs='1' maxOccurs='1'>
      <xsd:element name='contrato' type='xsd:long' minOccurs='0' />
      <xsd:element name='sincronizarBases' type='xsd:boolean' minOccurs='0' />
    </xsd:sequence>
  </xsd:complexType>
</xsd:schema>
 
<xsd:schema targetNamespace='cadastro.beg.tfs.totvs.com' attributeFormDefault='unqualified' elementFormDefault='unqualified' xmlns:xsd='http://www.w3.org/2001/XMLSchema' xmlns:tns='cadastro.beg.tfs.totvs.com'>
  <xsd:element name='buscarContrato' type='tns:buscarContrato' />
  <xsd:complexType name='buscarContrato'>
    <xsd:sequence minOccurs='1' maxOccurs='1'>
      <xsd:element name='contrato' type='xsd:long' minOccurs='0' />
      <xsd:element name='sincronizarBases' type='xsd:boolean' minOccurs='0' />
      <xsd:element name='forcarSincronizacao' type='xsd:boolean' minOccurs='0' />
    </xsd:sequence>
  </xsd:complexType>
</xsd:schema>