e.Toscana Compliance 
Request for Comments: 1 
Del: 15/01/2007 
Categoria: Applicativa
Destinatari: Regione Toscana, Comuni, Amministrazioni locali

Servizi SUPA per i Portali a cittadini ed Imprese
 
Indice
------
1. Contesto di riferimento ed obiettivi
2. Integrazione dei sistemi informativi
3. Prodotti attesi
4. Bibliografia

1.	Contesto di riferimento ed obiettivi
---------------------------------------
L'attuazione di un portale di e-government, nellabito dei servizi SUAP (Sportello Unico delle attivit produttive), 
prevede il colloquio tra il sistema portale ed il sistema di backoffice.
Tale colloquio  bidirezionale in qualto e prevede:
- linvio delle richieste del cittadino/impresa allEnte
- la consultazione dei dati della pratica da parte del Portale.
In questo contesto il colloquio tra i due sistemi  punt-a-punto e non prevede il coinvolgimento di altri sistemi.

La definizione e l'applicazione di questo protocollo di cooperazione offre una molteplicit di vantaggi: 
*	Favorisce la Cooperazione applicativa
*	Migliora lAccessibilit dei servizi
*	Permette lIntercambiabilit dei Componenti applicativi
*	Favorisce la Modularit di attivazione nuovi Enti

2.	Integrazione dei sistemi informativi
---------------------------------------
Il presente documento descrive i Web-Method necessari alle funzione di monitoraggio, visualizzazione ed 
attivazione delle pratiche o procedimenti amministrativi.
	visualizzazione elenco pratiche di un soggetto;
	visualizzazione dettaglio stato pratica;
	attivazione di un procedimento amministrativo;
	estrazione allegato.

In particolare si descrive linterfaccia del WebServices ws_pratiche ed i relativi WebMethod necessari 
allattivazione dei servizi precedentemente indicati.

Il seguente prospetto descrve, per ogni WebMethod, la funzionalit fornita.
- wm_lista_procedimenti: Consultazione elenco pratiche di un soggetto	
- wm_procedimento: Consultazione dettagli stato pratica		
- wm_attiva_procedimento: Attivazione procedimento amministrativo		
- wm_doc: Consultazione documenti allegati		
- wm_oneri: Visualizzazione della situazione che riguarda gli oneri e le relative rate da pagare e/o quelle gi pagate legate ad un procedimento		
- wm_lista_oneri: Lista degli oneri legati ad un soggetto		
- wm_pagato: Inserimento della data di pagamento		


3.	Prodotti attesi
---------------------------------------

3.	Struttura Web-Service
La presente sezione descrive linterfaccia di ciascun WebMethod del WebService 
WS_PRATICHE. Il comportamento dei WebService e linterfaccia di tutti i suoi metodi pu 
essere descritta dal seguente documento WSDL (Web Service Definition Language).

<?xml version="1.0" encoding="utf-8" ?> 
- <definitions xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" 
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s="http://www.w3.org/2001/XMLSchema" 
xmlns:s0="http://localhost:/aspnet/ws_pratiche/schema" 
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" 
xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" 
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" 
targetNamespace="http://localhost:/aspnet/ws_pratiche/schema" xmlns="http://schemas.xmlsoap.org/wsdl/">
- <types>
- <s:schema elementFormDefault="qualified" 
targetNamespace="http://localhost:/aspnet/ws_pratiche/schema">
- <s:element name="wm_lista_procedimenti">
- <s:complexType>
- <s:sequence>
  <s:element minOccurs="0" maxOccurs="1" name="ls_cod_fis" type="s:string" /> 
  <s:element minOccurs="0" maxOccurs="1" name="ls_sesid" type="s:string" /> 
  <s:element minOccurs="0" maxOccurs="1" name="ls_dtinizio" type="s:string" /> 
  <s:element minOccurs="0" maxOccurs="1" name="ls_dtfine" type="s:string" /> 
  <s:element minOccurs="0" maxOccurs="1" name="ls_stato" type="s:string" /> 
  </s:sequence>
  </s:complexType>
  </s:element>
- <s:element name="wm_lista_procedimentiResponse">
- <s:complexType>
- <s:sequence>
  <s:element minOccurs="0" maxOccurs="1" name="wm_lista_procedimentiResult" type="s:string" /> 
  </s:sequence>
  </s:complexType>
  </s:element>
- <s:element name="wm_procedimento">
- <s:complexType>
- <s:sequence>
  <s:element minOccurs="1" maxOccurs="1" name="li_idproc" type="s:long" /> 
  </s:sequence>
  </s:complexType>
  </s:element>
- <s:element name="wm_procedimentoResponse">
- <s:complexType>
- <s:sequence>
  <s:element minOccurs="0" maxOccurs="1" name="wm_procedimentoResult" type="s:string" /> 
  </s:sequence>
  </s:complexType>
  </s:element>
- <s:element name="wm_attiva_procedimento">
- <s:complexType>
- <s:sequence>
  <s:element minOccurs="0" maxOccurs="1" name="codice_fiscale_titolare" type="s:string" /> 
  <s:element minOccurs="0" maxOccurs="1" name="anagrafica_titolare" type="s:string" /> 
  <s:element minOccurs="0" maxOccurs="1" name="codice_fiscale_richiedente" type="s:string" /> 
  <s:element minOccurs="0" maxOccurs="1" name="anagrafica_richiedente" type="s:string" /> 
  <s:element minOccurs="0" maxOccurs="1" name="tipo_procedimento" type="s:string" /> 
  <s:element minOccurs="0" maxOccurs="1" name="dati_procedimento" type="s:string" /> 
  <s:element minOccurs="0" maxOccurs="1" name="argomento" type="s:string" /> 
  <s:element minOccurs="0" maxOccurs="1" name="xml_richiesta" type="s:string" /> 
  </s:sequence>
  </s:complexType>
  </s:element>
- <s:element name="wm_attiva_procedimentoResponse">
- <s:complexType>
- <s:sequence>
  <s:element minOccurs="0" maxOccurs="1" name="wm_attiva_procedimentoResult" type="s:string" /> 
  </s:sequence>
  </s:complexType>
  </s:element>
- <s:element name="wm_doc">
- <s:complexType>
- <s:sequence>
  <s:element minOccurs="1" maxOccurs="1" name="blo_id" type="s:long" /> 
  </s:sequence>
  </s:complexType>
  </s:element>
- <s:element name="wm_docResponse">
- <s:complexType>
- <s:sequence>
  <s:element minOccurs="0" maxOccurs="1" name="wm_docResult" type="s:string" /> 
  </s:sequence>
  </s:complexType>
  </s:element>
- <s:element name="wm_lista_oneri">
- <s:complexType>
- <s:sequence>
  <s:element minOccurs="0" maxOccurs="1" name="codice_fiscale" type="s:string" /> 
  <s:element minOccurs="0" maxOccurs="1" name="filtro" type="s:string" /> 
  </s:sequence>
  </s:complexType>
  </s:element>
- <s:element name="wm_lista_oneriResponse">
- <s:complexType>
- <s:sequence>
  <s:element minOccurs="0" maxOccurs="1" name="wm_lista_oneriResult" type="s:string" /> 
  </s:sequence>
  </s:complexType>
  </s:element>
- <s:element name="wm_oneri">
- <s:complexType>
- <s:sequence>
  <s:element minOccurs="1" maxOccurs="1" name="docid" type="s:long" /> 
  </s:sequence>
  </s:complexType>
  </s:element>
- <s:element name="wm_oneriResponse">
- <s:complexType>
- <s:sequence>
  <s:element minOccurs="0" maxOccurs="1" name="wm_oneriResult" type="s:string" /> 
  </s:sequence>
  </s:complexType>
  </s:element>
- <s:element name="wm_pagato">
- <s:complexType>
- <s:sequence>
  <s:element minOccurs="0" maxOccurs="1" name="ls_oneri" type="s:string" /> 
  </s:sequence>
  </s:complexType>
  </s:element>
- <s:element name="wm_pagatoResponse">
- <s:complexType>
- <s:sequence>
  <s:element minOccurs="0" maxOccurs="1" name="wm_pagatoResult" type="s:string" /> 
  </s:sequence>
  </s:complexType>
  </s:element>
  <s:element name="string" nillable="true" type="s:string" /> 
  </s:schema>
  </types>
- <message name="wm_lista_procedimentiSoapIn">
  <part name="parameters" element="s0:wm_lista_procedimenti" /> 
  </message>
- <message name="wm_lista_procedimentiSoapOut">
  <part name="parameters" element="s0:wm_lista_procedimentiResponse" /> 
  </message>
- <message name="wm_procedimentoSoapIn">
  <part name="parameters" element="s0:wm_procedimento" /> 
  </message>
- <message name="wm_procedimentoSoapOut">
  <part name="parameters" element="s0:wm_procedimentoResponse" /> 
  </message>
- <message name="wm_attiva_procedimentoSoapIn">
  <part name="parameters" element="s0:wm_attiva_procedimento" /> 
  </message>
- <message name="wm_attiva_procedimentoSoapOut">
  <part name="parameters" element="s0:wm_attiva_procedimentoResponse" /> 
  </message>
- <message name="wm_docSoapIn">
  <part name="parameters" element="s0:wm_doc" /> 
  </message>
- <message name="wm_docSoapOut">
  <part name="parameters" element="s0:wm_docResponse" /> 
  </message>
- <message name="wm_lista_oneriSoapIn">
  <part name="parameters" element="s0:wm_lista_oneri" /> 
  </message>
- <message name="wm_lista_oneriSoapOut">
  <part name="parameters" element="s0:wm_lista_oneriResponse" /> 
  </message>
- <message name="wm_oneriSoapIn">
  <part name="parameters" element="s0:wm_oneri" /> 
  </message>
- <message name="wm_oneriSoapOut">
  <part name="parameters" element="s0:wm_oneriResponse" /> 
  </message>
- <message name="wm_pagatoSoapIn">
  <part name="parameters" element="s0:wm_pagato" /> 
  </message>
- <message name="wm_pagatoSoapOut">
  <part name="parameters" element="s0:wm_pagatoResponse" /> 
  </message>
- <message name="wm_lista_procedimentiHttpGetIn">
  <part name="ls_cod_fis" type="s:string" /> 
  <part name="ls_sesid" type="s:string" /> 
  <part name="ls_dtinizio" type="s:string" /> 
  <part name="ls_dtfine" type="s:string" /> 
  <part name="ls_stato" type="s:string" /> 
  </message>
- <message name="wm_lista_procedimentiHttpGetOut">
  <part name="Body" element="s0:string" /> 
  </message>
- <message name="wm_procedimentoHttpGetIn">
  <part name="li_idproc" type="s:string" /> 
  </message>
- <message name="wm_procedimentoHttpGetOut">
  <part name="Body" element="s0:string" /> 
  </message>
- <message name="wm_attiva_procedimentoHttpGetIn">
  <part name="codice_fiscale_titolare" type="s:string" /> 
  <part name="anagrafica_titolare" type="s:string" /> 
  <part name="codice_fiscale_richiedente" type="s:string" /> 
  <part name="anagrafica_richiedente" type="s:string" /> 
  <part name="tipo_procedimento" type="s:string" /> 
  <part name="dati_procedimento" type="s:string" /> 
  <part name="argomento" type="s:string" /> 
  <part name="xml_richiesta" type="s:string" /> 
  </message>
- <message name="wm_attiva_procedimentoHttpGetOut">
  <part name="Body" element="s0:string" /> 
  </message>
- <message name="wm_docHttpGetIn">
  <part name="blo_id" type="s:string" /> 
  </message>
- <message name="wm_docHttpGetOut">
  <part name="Body" element="s0:string" /> 
  </message>
- <message name="wm_lista_oneriHttpGetIn">
  <part name="codice_fiscale" type="s:string" /> 
  <part name="filtro" type="s:string" /> 
  </message>
- <message name="wm_lista_oneriHttpGetOut">
  <part name="Body" element="s0:string" /> 
  </message>
- <message name="wm_oneriHttpGetIn">
  <part name="docid" type="s:string" /> 
  </message>
- <message name="wm_oneriHttpGetOut">
  <part name="Body" element="s0:string" /> 
  </message>
- <message name="wm_pagatoHttpGetIn">
  <part name="ls_oneri" type="s:string" /> 
  </message>
- <message name="wm_pagatoHttpGetOut">
  <part name="Body" element="s0:string" /> 
  </message>
- <message name="wm_lista_procedimentiHttpPostIn">
  <part name="ls_cod_fis" type="s:string" /> 
  <part name="ls_sesid" type="s:string" /> 
  <part name="ls_dtinizio" type="s:string" /> 
  <part name="ls_dtfine" type="s:string" /> 
  <part name="ls_stato" type="s:string" /> 
  </message>
- <message name="wm_lista_procedimentiHttpPostOut">
  <part name="Body" element="s0:string" /> 
  </message>
- <message name="wm_procedimentoHttpPostIn">
  <part name="li_idproc" type="s:string" /> 
  </message>
- <message name="wm_procedimentoHttpPostOut">
  <part name="Body" element="s0:string" /> 
  </message>
- <message name="wm_attiva_procedimentoHttpPostIn">
  <part name="codice_fiscale_titolare" type="s:string" /> 
  <part name="anagrafica_titolare" type="s:string" /> 
  <part name="codice_fiscale_richiedente" type="s:string" /> 
  <part name="anagrafica_richiedente" type="s:string" /> 
  <part name="tipo_procedimento" type="s:string" /> 
  <part name="dati_procedimento" type="s:string" /> 
  <part name="argomento" type="s:string" /> 
  <part name="xml_richiesta" type="s:string" /> 
  </message>
- <message name="wm_attiva_procedimentoHttpPostOut">
  <part name="Body" element="s0:string" /> 
  </message>
- <message name="wm_docHttpPostIn">
  <part name="blo_id" type="s:string" /> 
  </message>
- <message name="wm_docHttpPostOut">
  <part name="Body" element="s0:string" /> 
  </message>
- <message name="wm_lista_oneriHttpPostIn">
  <part name="codice_fiscale" type="s:string" /> 
  <part name="filtro" type="s:string" /> 
  </message>
- <message name="wm_lista_oneriHttpPostOut">
  <part name="Body" element="s0:string" /> 
  </message>
- <message name="wm_oneriHttpPostIn">
  <part name="docid" type="s:string" /> 
  </message>
- <message name="wm_oneriHttpPostOut">
  <part name="Body" element="s0:string" /> 
  </message>
- <message name="wm_pagatoHttpPostIn">
  <part name="ls_oneri" type="s:string" /> 
  </message>
- <message name="wm_pagatoHttpPostOut">
  <part name="Body" element="s0:string" /> 
  </message>
- <portType name="WS_praticheSoap">
- <operation name="wm_lista_procedimenti">
  <input message="s0:wm_lista_procedimentiSoapIn" /> 
  <output message="s0:wm_lista_procedimentiSoapOut" /> 
  </operation>
- <operation name="wm_procedimento">
  <input message="s0:wm_procedimentoSoapIn" /> 
  <output message="s0:wm_procedimentoSoapOut" /> 
  </operation>
- <operation name="wm_attiva_procedimento">
  <input message="s0:wm_attiva_procedimentoSoapIn" /> 
  <output message="s0:wm_attiva_procedimentoSoapOut" /> 
  </operation>
- <operation name="wm_doc">
  <input message="s0:wm_docSoapIn" /> 
  <output message="s0:wm_docSoapOut" /> 
  </operation>
- <operation name="wm_lista_oneri">
  <input message="s0:wm_lista_oneriSoapIn" /> 
  <output message="s0:wm_lista_oneriSoapOut" /> 
  </operation>
- <operation name="wm_oneri">
  <input message="s0:wm_oneriSoapIn" /> 
  <output message="s0:wm_oneriSoapOut" /> 
  </operation>
- <operation name="wm_pagato">
  <input message="s0:wm_pagatoSoapIn" /> 
  <output message="s0:wm_pagatoSoapOut" /> 
  </operation>
  </portType>
- <portType name="WS_praticheHttpGet">
- <operation name="wm_lista_procedimenti">
  <input message="s0:wm_lista_procedimentiHttpGetIn" /> 
  <output message="s0:wm_lista_procedimentiHttpGetOut" /> 
  </operation>
- <operation name="wm_procedimento">
  <input message="s0:wm_procedimentoHttpGetIn" /> 
  <output message="s0:wm_procedimentoHttpGetOut" /> 
  </operation>
- <operation name="wm_attiva_procedimento">
  <input message="s0:wm_attiva_procedimentoHttpGetIn" /> 
  <output message="s0:wm_attiva_procedimentoHttpGetOut" /> 
  </operation>
- <operation name="wm_doc">
  <input message="s0:wm_docHttpGetIn" /> 
  <output message="s0:wm_docHttpGetOut" /> 
  </operation>
- <operation name="wm_lista_oneri">
  <input message="s0:wm_lista_oneriHttpGetIn" /> 
  <output message="s0:wm_lista_oneriHttpGetOut" /> 
  </operation>
- <operation name="wm_oneri">
  <input message="s0:wm_oneriHttpGetIn" /> 
  <output message="s0:wm_oneriHttpGetOut" /> 
  </operation>
- <operation name="wm_pagato">
  <input message="s0:wm_pagatoHttpGetIn" /> 
  <output message="s0:wm_pagatoHttpGetOut" /> 
  </operation>
  </portType>
- <portType name="WS_praticheHttpPost">
- <operation name="wm_lista_procedimenti">
  <input message="s0:wm_lista_procedimentiHttpPostIn" /> 
  <output message="s0:wm_lista_procedimentiHttpPostOut" /> 
  </operation>
- <operation name="wm_procedimento">
  <input message="s0:wm_procedimentoHttpPostIn" /> 
  <output message="s0:wm_procedimentoHttpPostOut" /> 
  </operation>
- <operation name="wm_attiva_procedimento">
  <input message="s0:wm_attiva_procedimentoHttpPostIn" /> 
  <output message="s0:wm_attiva_procedimentoHttpPostOut" /> 
  </operation>
- <operation name="wm_doc">
  <input message="s0:wm_docHttpPostIn" /> 
  <output message="s0:wm_docHttpPostOut" /> 
  </operation>
- <operation name="wm_lista_oneri">
  <input message="s0:wm_lista_oneriHttpPostIn" /> 
  <output message="s0:wm_lista_oneriHttpPostOut" /> 
  </operation>
- <operation name="wm_oneri">
  <input message="s0:wm_oneriHttpPostIn" /> 
  <output message="s0:wm_oneriHttpPostOut" /> 
  </operation>
- <operation name="wm_pagato">
  <input message="s0:wm_pagatoHttpPostIn" /> 
  <output message="s0:wm_pagatoHttpPostOut" /> 
  </operation>
  </portType>
- <binding name="WS_praticheSoap" type="s0:WS_praticheSoap">
  <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document" /> 
- <operation name="wm_lista_procedimenti">
  <soap:operation soapAction="http://localhost:/aspnet/ws_pratiche/schema/wm_lista_procedimenti" 
style="document" /> 
- <input>
  <soap:body use="literal" /> 
  </input>
- <output>
  <soap:body use="literal" /> 
  </output>
  </operation>
- <operation name="wm_procedimento">
  <soap:operation soapAction="http://localhost:/aspnet/ws_pratiche/schema/wm_procedimento" 
style="document" /> 
- <input>
  <soap:body use="literal" /> 
  </input>
- <output>
  <soap:body use="literal" /> 
  </output>
  </operation>
- <operation name="wm_attiva_procedimento">
  <soap:operation soapAction="http://localhost:/aspnet/ws_pratiche/schema/wm_attiva_procedimento" 
style="document" /> 
- <input>
  <soap:body use="literal" /> 
  </input>
- <output>
  <soap:body use="literal" /> 
  </output>
  </operation>
- <operation name="wm_doc">
  <soap:operation soapAction="http://localhost:/aspnet/ws_pratiche/schema/wm_doc" style="document" /> 
- <input>
  <soap:body use="literal" /> 
  </input>
- <output>
  <soap:body use="literal" /> 
  </output>
  </operation>
- <operation name="wm_lista_oneri">
  <soap:operation soapAction="http://localhost:/aspnet/ws_pratiche/schema/wm_lista_oneri" style="document" 
/> 
- <input>
  <soap:body use="literal" /> 
  </input>
- <output>
  <soap:body use="literal" /> 
  </output>
  </operation>
- <operation name="wm_oneri">
  <soap:operation soapAction="http://localhost:/aspnet/ws_pratiche/schema/wm_oneri" style="document" /> 
- <input>
  <soap:body use="literal" /> 
  </input>
- <output>
  <soap:body use="literal" /> 
  </output>
  </operation>
- <operation name="wm_pagato">
  <soap:operation soapAction="http://localhost:/aspnet/ws_pratiche/schema/wm_pagato" style="document" /> 
- <input>
  <soap:body use="literal" /> 
  </input>
- <output>
  <soap:body use="literal" /> 
  </output>
  </operation>
  </binding>
- <binding name="WS_praticheHttpGet" type="s0:WS_praticheHttpGet">
  <http:binding verb="GET" /> 
- <operation name="wm_lista_procedimenti">
  <http:operation location="/wm_lista_procedimenti" /> 
- <input>
  <http:urlEncoded /> 
  </input>
- <output>
  <mime:mimeXml part="Body" /> 
  </output>
  </operation>
- <operation name="wm_procedimento">
  <http:operation location="/wm_procedimento" /> 
- <input>
  <http:urlEncoded /> 
  </input>
- <output>
  <mime:mimeXml part="Body" /> 
  </output>
  </operation>
- <operation name="wm_attiva_procedimento">
  <http:operation location="/wm_attiva_procedimento" /> 
- <input>
  <http:urlEncoded /> 
  </input>
- <output>
  <mime:mimeXml part="Body" /> 
  </output>
  </operation>
- <operation name="wm_doc">
  <http:operation location="/wm_doc" /> 
- <input>
  <http:urlEncoded /> 
  </input>
- <output>
  <mime:mimeXml part="Body" /> 
  </output>
  </operation>
- <operation name="wm_lista_oneri">
  <http:operation location="/wm_lista_oneri" /> 
- <input>
  <http:urlEncoded /> 
  </input>
- <output>
  <mime:mimeXml part="Body" /> 
  </output>
  </operation>
- <operation name="wm_oneri">
  <http:operation location="/wm_oneri" /> 
- <input>
  <http:urlEncoded /> 
  </input>
- <output>
  <mime:mimeXml part="Body" /> 
  </output>
  </operation>
- <operation name="wm_pagato">
  <http:operation location="/wm_pagato" /> 
- <input>
  <http:urlEncoded /> 
  </input>
- <output>
  <mime:mimeXml part="Body" /> 
  </output>
  </operation>
  </binding>
- <binding name="WS_praticheHttpPost" type="s0:WS_praticheHttpPost">
  <http:binding verb="POST" /> 
- <operation name="wm_lista_procedimenti">
  <http:operation location="/wm_lista_procedimenti" /> 
- <input>
  <mime:content type="application/x-www-form-urlencoded" /> 
  </input>
- <output>
  <mime:mimeXml part="Body" /> 
  </output>
  </operation>
- <operation name="wm_procedimento">
  <http:operation location="/wm_procedimento" /> 
- <input>
  <mime:content type="application/x-www-form-urlencoded" /> 
  </input>
- <output>
  <mime:mimeXml part="Body" /> 
  </output>
  </operation>
- <operation name="wm_attiva_procedimento">
  <http:operation location="/wm_attiva_procedimento" /> 
- <input>
  <mime:content type="application/x-www-form-urlencoded" /> 
  </input>
- <output>
  <mime:mimeXml part="Body" /> 
  </output>
  </operation>
- <operation name="wm_doc">
  <http:operation location="/wm_doc" /> 
- <input>
  <mime:content type="application/x-www-form-urlencoded" /> 
  </input>
- <output>
  <mime:mimeXml part="Body" /> 
  </output>
  </operation>
- <operation name="wm_lista_oneri">
  <http:operation location="/wm_lista_oneri" /> 
- <input>
  <mime:content type="application/x-www-form-urlencoded" /> 
  </input>
- <output>
  <mime:mimeXml part="Body" /> 
  </output>
  </operation>
- <operation name="wm_oneri">
  <http:operation location="/wm_oneri" /> 
- <input>
  <mime:content type="application/x-www-form-urlencoded" /> 
  </input>
- <output>
  <mime:mimeXml part="Body" /> 
  </output>
  </operation>
- <operation name="wm_pagato">
  <http:operation location="/wm_pagato" /> 
- <input>
  <mime:content type="application/x-www-form-urlencoded" /> 
  </input>
- <output>
  <mime:mimeXml part="Body" /> 
  </output>
  </operation>
  </binding>
- <service name="WS_pratiche">
- <port name="WS_praticheSoap" binding="s0:WS_praticheSoap">
  <soap:address location="http://localhost/aspnet/WS_PRATICHE/ws_pratiche.asmx" /> 
  </port>
- <port name="WS_praticheHttpGet" binding="s0:WS_praticheHttpGet">
  <http:address location="http://localhost/aspnet/WS_PRATICHE/ws_pratiche.asmx" /> 
  </port>
- <port name="WS_praticheHttpPost" binding="s0:WS_praticheHttpPost">
  <http:address location="http://localhost/aspnet/WS_PRATICHE/ws_pratiche.asmx" /> 
  </port>
  </service>
  </definitions>

3.1	Web-Method: wm_lista_procedimenti

[WebMethod]
string wm_lista_procedimenti (string ls_cod_fis, string ls_sesid, string 
ls_dtinizio, string ls_dtfine, string ls_stato)

Argomenti
Wm_lista_procedimenti: stringa contenente documento XML con elenco dei 
procedimento amministrativi attivi per il soggetto indicato in entrata.
ls_cod_fis: codice fiscale del soggetto (persona fisica/giuridica)
ls_sesid: sessione
ls_dtinizio: procedimenti validi dal
ls_dtfine: procedimenti validi al 
ls_stato: In corso, Terminati, Tutti

Scopo
acquisizione della lista dei procedimenti amministrativi attivi per il soggetto in input.

Messaggio SOAP per linvocazione del servizio.

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

<soap:Envelope 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <wm_lista_procedimenti 
xmlns="http://localhost:/aspnet/ws_pratiche/schema">
      <ls_cod_fis>string</ls_cod_fis>
      <ls_sesid>string</ls_sesid>
      <ls_dtinizio>string</ls_dtinizio>
      <ls_dtfine>string</ls_dtfine>
      <ls_stato>string</ls_stato>
    </wm_lista_procedimenti>
  </soap:Body>
</soap:Envelope>

Messaggio SOAP di risposta

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

<soap:Envelope 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <wm_lista_procedimentiResponse 
xmlns="http://localhost:/aspnet/ws_pratiche/schema">
      <wm_lista_procedimentiResult>string</wm_lista_procedimentiResult>
    </wm_lista_procedimentiResponse>
  </soap:Body>
</soap:Envelope>

Il documento XML contenuto nel campo stringa possiede la  struttura gerarchica descritta dal seguente schema XSD (XML 
Schema Definition).

<?xml version="1.0" encoding="ISO-8859-1"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" 
attributeFormDefault="unqualified">
	<xs:element name="wm_lista_procedimenti">
		<xs:annotation>
			<xs:documentation>lista procedimenti</xs:documentation>
		</xs:annotation>
		<xs:complexType>
			<xs:sequence>
				<xs:element name="procedimenti" maxOccurs="unbounded">
					<xs:complexType>
						<xs:sequence>
							<xs:element name="lpr_id" type="xs:long" minOccurs="0">
								<xs:annotation>
									<xs:documentation>Id di riferimento (token) del procedimento (pratica)</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="lpr_annorif" type="xs:integer" minOccurs="0">
								<xs:annotation>
									<xs:documentation>Anno di riferimento</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="lpr_nrprot" type="xs:long" minOccurs="0">
								<xs:annotation>
									<xs:documentation>Numero di protocollo della pratica </xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="lpr_dtprot" type="xs:date" minOccurs="0">
								<xs:annotation>
									<xs:documentation>Data di protocollo della pratica</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="lpr_tipopr" type="xs:string" minOccurs="0"/>
							<xs:element name="lpr_oggetto" type="xs:string" minOccurs="0">
								<xs:annotation>
									<xs:documentation>Oggetto della pratica</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="esiste_dettaglio" type="xs:string" minOccurs="0"/>
						</xs:sequence>
					</xs:complexType>
				</xs:element>
			</xs:sequence>
		</xs:complexType>
	</xs:element>
</xs:schema>


Esempio di schema XML congruente con lo schema XSD sopra descritto:

<?xml version="1.0" encoding="ISO-8859-1"?>
<wm_lista_procedimenti xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:noNamespaceSchemaLocation="http://www.cedaf.it/schema/Procedimenti/wm_lista_procedimenti.xsd">
	<procedimenti>
		<lpr_id>1</lpr_id>
		<lpr_annorif>2003</lpr_annorif>
		<lpr_nrprot>267</lpr_nrprot>
		<lpr_dtprot>2003-01-25</lpr_dtprot>
		<lpr_tipopr>concessione edilizia</lpr_tipopr>
		<lpr_oggetto>Nuova costruzione</lpr_oggetto>
		<esiste_dettaglio>S</esiste_dettaglio>
	</procedimenti>
	<procedimenti>
		<lpr_id>2</lpr_id>
		<lpr_annorif>2003</lpr_annorif>
		<lpr_nrprot>565</lpr_nrprot>
		<lpr_dtprot>2003-03-15</lpr_dtprot>
		<lpr_tipopr>concessione edilizia</lpr_tipopr>
		<lpr_oggetto>Cambio residenza</lpr_oggetto>
		<esiste_dettaglio>S</esiste_dettaglio>
	</procedimenti>
</wm_lista_procedimenti>





3.2	Web-Method: wm_procedimento

[WebMethod]
string wm_procedimento (long li_idproc)

argomenti
wm_procedimento: stringa contenente documento XML con i dettagli del 
procedimento amministrativo.
li_idproc: identificativo del procedimento;

Scopo
acquisizione di tutti gli attributi del procedimento amministrativo indicato in input.

Messaggio SOAP per linvocazione del servizio.

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"  
               xmlns:xsd=http://www.w3.org/2001/XMLSchema
               xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <wm_procedimento xmlns="http://localhost:/aspnet/ws_pratiche/schema">
      <li_idproc>long</li_idproc>
    </wm_procedimento>
  </soap:Body>
</soap:Envelope>
Messaggio SOAP di risposta
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <wm_procedimentoResponse xmlns="http://www.cedaf.it/schema/">
      <wm_procedimentoResult>string</wm_procedimentoResult>
    </wm_procedimentoResponse>
  </soap:Body>
</soap:Envelope>

Il documento XML restituito dal WebMethod rappresenta una classe con la seguente 
struttura gerarchica:

<Procedimento>
       (lista attributi) ...


La struttura XML  riconducibile al seguente schema XSD (XML 
Schema Definition).

<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- edited with XMLSPY v5 rel. 3 U (http://www.xmlspy.com) by RICCI CLAUDIO (CEDAF SRL) -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" 
attributeFormDefault="unqualified">
	<xs:element name="wm_procedimento">
		<xs:annotation>
			<xs:documentation>procedimento</xs:documentation>
		</xs:annotation>
		<xs:complexType>
			<xs:sequence>
				<xs:element name="pro_id" type="xs:long" minOccurs="0">
					<xs:annotation>
						<xs:documentation>Id di riferimento (token) del procedimento (pratica)</xs:documentation>
					</xs:annotation>
				</xs:element>
				<xs:element name="pro_annorif" type="xs:integer" minOccurs="0">
					<xs:annotation>
						<xs:documentation>Anno di riferimento</xs:documentation>
					</xs:annotation>
				</xs:element>
				<xs:element name="pro_nrprot" type="xs:long" minOccurs="0">
					<xs:annotation>
						<xs:documentation>Numero di protocollo della pratica </xs:documentation>
					</xs:annotation>
				</xs:element>
				<xs:element name="pro_dtprot" type="xs:date" minOccurs="0">
					<xs:annotation>
						<xs:documentation>Data di protocollo della pratica</xs:documentation>
					</xs:annotation>
				</xs:element>
				<xs:element name="pro_oggetto" type="xs:string" minOccurs="0">
					<xs:annotation>
						<xs:documentation>Oggetto della pratica</xs:documentation>
					</xs:annotation>
				</xs:element>
				<xs:element name="pro_respon" type="xs:string" minOccurs="0">
					<xs:annotation>
						<xs:documentation>Riferimenti al responsabile del procedimento</xs:documentation>
					</xs:annotation>
				</xs:element>
				<xs:element name="pro_dtinizio" type="xs:date" minOccurs="0">
					<xs:annotation>
						<xs:documentation>Data inizio del procedimento</xs:documentation>
					</xs:annotation>
				</xs:element>
				<xs:element name="pro_dtfine" type="xs:date" minOccurs="0">
					<xs:annotation>
						<xs:documentation>Data Fine del procedimento</xs:documentation>
					</xs:annotation>
				</xs:element>
				<xs:element name="pro_ggteor" type="xs:integer" minOccurs="0">
					<xs:annotation>
						<xs:documentation>Numero di giorni teorico massimo del procedimento</xs:documentation>
					</xs:annotation>
				</xs:element>
				<xs:element name="pro_ggeff" type="xs:integer" minOccurs="0">
					<xs:annotation>
						<xs:documentation>Numero di giorni effettivi di turata del procedimento</xs:documentation>
					</xs:annotation>
				</xs:element>
				<xs:element name="pro_ggmanc" type="xs:integer" minOccurs="0">
					<xs:annotation>
						<xs:documentation>Numero di giorni mancanti alla conclusione del procedimento</xs:documentation>
					</xs:annotation>
				</xs:element>
				<xs:element name="pro_stato" type="xs:string" minOccurs="0">
					<xs:annotation>
						<xs:documentation>Stato procedimento</xs:documentation>
					</xs:annotation>
				</xs:element>
				<xs:element name="fase" minOccurs="0" maxOccurs="unbounded">
					<xs:annotation>
						<xs:documentation>Fasi del proceimento</xs:documentation>
					</xs:annotation>
					<xs:complexType>
						<xs:sequence>
							<xs:element name="pro_fdescr" type="xs:string" minOccurs="0">
								<xs:annotation>
									<xs:documentation>Descrizione della fase</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="pro_frespon" type="xs:string" minOccurs="0">
								<xs:annotation>
									<xs:documentation>Riferimenti al responsabile della fase procedimento</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="pro_fstato" type="xs:string" minOccurs="0">
								<xs:annotation>
									<xs:documentation>_terminato_,_in corso_ ,_sospeso_</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="pro_fnote" type="xs:string" minOccurs="0">
								<xs:annotation>
									<xs:documentation>Note allo stato della fase</xs:documentation>
								</xs:annotation>
							</xs:element>
						</xs:sequence>
					</xs:complexType>
				</xs:element>
				<xs:element name="pro_all" minOccurs="0" maxOccurs="unbounded">
					<xs:annotation>
						<xs:documentation>Allegati procedimento </xs:documentation>
					</xs:annotation>
					<xs:complexType>
						<xs:sequence>
							<xs:element name="pro_serial" type="xs:long" minOccurs="0">
								<xs:annotation>
									<xs:documentation>Serial dell'allegato</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="pro_commento" type="xs:string" minOccurs="0">
								<xs:annotation>
									<xs:documentation>Commento dell'allegato</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="pro_idtipoall" type="xs:string" minOccurs="0">
								<xs:annotation>
									<xs:documentation>Codice estensione del file allegato</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="pro_nomefile" minOccurs="0">
								<xs:annotation>
									<xs:documentation>Nome del file allegato nel caso in cui il file  generico 
</xs:documentation>
								</xs:annotation>
							</xs:element>
						</xs:sequence>
					</xs:complexType>
				</xs:element>
			</xs:sequence>
		</xs:complexType>
	</xs:element>
</xs:schema>


Esempio di schema XML congruente con lo schema XSD sopra descritto:

<?xml version="1.0" encoding="ISO-8859-1"?>
<wm_lista_procedimenti xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:noNamespaceSchemaLocation="http://www.cedaf.it/schema/Procedimenti/wm_procedimento.xsd">
	<pro_id>1</pro_id>
	<pro_annorif>2003</pro_annorif>
	<pro_nrprot>267</pro_nrprot>
	<pro_dtprot>2003-01-25</pro_dtprot>
	<pro_oggetto>Nuova costruzione</pro_oggetto>
	<pro_respon>Giovanni Bianchi - gbianchi@cedaf.it</pro_respon>
	<pro_dtinizio>2003-01-01</pro_dtinizio>
	<pro_dtfine>2003-12-31</pro_dtfine>
	<pro_ggteor>365</pro_ggteor>
	<pro_ggeff>0</pro_ggeff>
	<pro_ggmanc>150</pro_ggmanc>
	<pro_stato>in corso</pro_stato>
	<fase>
		<pro_fdescr>acquisizione</pro_fdescr>
		<pro_frespon>Mario Rossi</pro_frespon>
		<pro_fstato>conclusa</pro_fstato>
	</fase>
	<fase>
		<pro_fdescr>istruttoria</pro_fdescr>
		<pro_frespon>Franco Verdi</pro_frespon>
		<pro_fstato>in corso</pro_fstato>
		<pro_fnote>commissione edilizia del mese prossimo</pro_fnote>
	</fase>
	<pro_all>
		<pro_serial>1375</pro_serial>
		<pro_commento>commento</pro_commento>
		<pro_idtipoall>0</pro_idtipoall>
		<pro_nomefile/>
	</pro_all>
	<pro_all>
		<pro_serial>1377</pro_serial>
		<pro_commento/>
		<pro_idtipoall>1</pro_idtipoall>
		<pro_nomefile/>
	</pro_all>
	<pro_all>
		<pro_serial>1376</pro_serial>
		<pro_commento/>
		<pro_idtipoall>5</pro_idtipoall>
		<pro_nomefile/>
	</pro_all>
	<pro_all>
		<pro_serial>1378</pro_serial>
		<pro_commento/>
		<pro_idtipoall>7</pro_idtipoall>
		<pro_nomefile>s\Documenti\Immagini\Immagini campione\Inverno.jpg</pro_nomefile>
	</pro_all>
</wm_procedimento>



3.3	Web-Method: wm_attiva_procedimento 

[WebMethod]
string wm_attiva_procedimento (string codice_fiscale_titolare, string 
anagrafica_titolare, string codice_fiscale_richiedente, string 
anagrafica_richiedente, string tipo_procedimento, string dati_procedimento, 
string argomento, string xml_richiesta)

argomenti
- wm_attiva_procedimento: stringa contenete il documento XML che riporta lesito e 
lID dellinoltro del procedimento
- codice_fiscale_titolare : identificativo del soggetto intestatario del  procedimento
- anagrafica_titolare: cognome/nome oppure ragione sociale dellintestatario del  
procedimento
- codice_fiscale_richiedente : identificativo del soggetto che attiva il procedimento
- anagrafica_richiedente: cognome/nome oppure ragione sociale del soggetto che 
attiva il procedimento
- tipo_procedimento: codifica del procedimento;
- dati_procedimento: documento XML contenente tutti gli attributi del procedimento 
amministrativo eventualmente gi attivato.
- argomento: breve descrizione della domanda (riportare alcuni attributi significativi del 
procedimento);
- xml_richiesta: documento XML contenente gli attributi necessari allattivazione del 
procedimento amministrativo. Tale documento avr una struttura variabile e 
dipendente dal tipo di procedimento amministrativo.

Scopo
Inoltro al sistema legacy della richiesta di attivazione di un procedimento 
amministrativo. Tale WebMethod sar invocato on-line in corrispondenza di ciascuna 
richiesta.

Messaggio SOAP per linvocazione del servizio

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <wm_attiva_procedimento xmlns="http://localhost:/aspnet/ws_pratiche/schema">
      <codice_fiscale_titolare>string</codice_fiscale_titolare>
      <anagrafica_titolare>string</anagrafica_titolare>
      <codice_fiscale_richiedente>string</codice_fiscale_richiedente>
      <anagrafica_richiedente>string</anagrafica_richiedente>
      <tipo_procedimento>string</tipo_procedimento>
      <dati_procedimento>string</dati_procedimento>
      <argomento>string</argomento>
      <xml_richiesta>string</xml_richiesta>
    </wm_attiva_procedimento>
  </soap:Body>
</soap:Envelope>

Messaggio SOAP di risposta

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <wm_attiva_procedimentoResponse 
xmlns="http://localhost:/aspnet/ws_pratiche/schema">
      <wm_attiva_procedimentoResult>string</wm_attiva_procedimentoResult>
    </wm_attiva_procedimentoResponse>
  </soap:Body>
</soap:Envelope>

ll documento XML restituito dal web-method: wm_attiva_procedimento possiede la 
seguente struttura gerarchica:
<attiva_procedimento>
       (lista attributi) ...
       

Schema XSD (XML Schema Definition):

<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" 
attributeFormDefault="unqualified">
	<xs:element name="attiva_procedimento">
		<xs:annotation>
			<xs:documentation>Esito del metodo attiva procedimento</xs:documentation>
		</xs:annotation>
		<xs:complexType>
			<xs:sequence>
				<xs:element name="pro_id" type="xs:long">
					<xs:annotation>
						<xs:documentation>id. procedimento </xs:documentation>
					</xs:annotation>
				</xs:element>
				<xs:element name="pro_nrprot" type="xs:long">
					<xs:annotation>
						<xs:documentation>numero protocollo</xs:documentation>
					</xs:annotation>
				</xs:element>
				<xs:element name="pro_dtprot" type="xs:date">
					<xs:annotation>
						<xs:documentation>data protocollo</xs:documentation>
					</xs:annotation>
				</xs:element>
				<xs:element name="pro_anno_proc" type="xs:int">
					<xs:annotation>
						<xs:documentation>anno di riferimento del protocollo</xs:documentation>
					</xs:annotation>
				</xs:element>
				<xs:element name="pro_dtarr" type="xs:date" minOccurs="0">
					<xs:annotation>
						<xs:documentation>Data arrivo procedimento da protocollare</xs:documentation>
					</xs:annotation>
				</xs:element>
				<xs:element name="pro_note" type="xs:string" minOccurs="0">
					<xs:annotation>
						<xs:documentation>Note attiva procedimento </xs:documentation>
					</xs:annotation>
				</xs:element>
			</xs:sequence>
		</xs:complexType>
	</xs:element>
</xs:schema>

Dati procedimento
Il documento XML del parametro di input dati_procedimento ha la seguente struttura 
gerarchica:

<dati_procedimento>
       (lista attributi) ...

La struttura XML   riconducibile al seguente schema XSD (XML 
Schema Definition).

<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" 
attributeFormDefault="unqualified">
	<xs:element name="dati_procedimento">
		<xs:annotation>
			<xs:documentation>Dati del procedimento attivato</xs:documentation>
		</xs:annotation>
		<xs:complexType>
			<xs:sequence>
				<xs:element name="pro_id" type="xs:long">
					<xs:annotation>
						<xs:documentation>id. procedimento </xs:documentation>
					</xs:annotation>
				</xs:element>
				<xs:element name="pro_nrprot" type="xs:long">
					<xs:annotation>
						<xs:documentation>numero protocollo</xs:documentation>
					</xs:annotation>
				</xs:element>
				<xs:element name="pro_dtprot" type="xs:date">
					<xs:annotation>
						<xs:documentation>data protocollo</xs:documentation>
					</xs:annotation>
				</xs:element>
				<xs:element name="pro_anno_proc" type="xs:int">
					<xs:annotation>
						<xs:documentation>anno di riferimento del protocollo</xs:documentation>
					</xs:annotation>
				</xs:element>
				<xs:element name="pro_respon" type="xs:string" minOccurs="0">
					<xs:annotation>
						<xs:documentation>responsabile del procedimento</xs:documentation>
					</xs:annotation>
				</xs:element>
				<xs:element name="pro_stato" type="xs:string" minOccurs="0">
					<xs:annotation>
						<xs:documentation>stato del procedimento</xs:documentation>
					</xs:annotation>
				</xs:element>
				<xs:element name="pro_dtarr" type="xs:date" minOccurs="0">
					<xs:annotation>
						<xs:documentation>Data arrivo procedimento da protocollare</xs:documentation>
					</xs:annotation>
				</xs:element>
				<xs:element name="pro_ricpro" type="xs:string" minOccurs="0">
					<xs:annotation>
						<xs:documentation>flag di richiesta protocollazione al procedimento</xs:documentation>
					</xs:annotation>
				</xs:element>
			</xs:sequence>
		</xs:complexType>
	</xs:element>
</xs:schema>


Esempio di schema XML congruente con lo schema XSD sopra descritto:

<?xml version="1.0" encoding="UTF-8"?>
<dati_procedimento xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation=" 
http:www.cedaf.it\schema\dati_procedimento.xsd">
	<pro_id>500</pro_id>
	<pro_nrprot>12654</pro_nrprot>
	<pro_dtprot>2003-11-19</pro_dtprot>
	<pro_anno_proc>2003</pro_anno_proc>
	<pro_respon>Lorenza Pirisi</pro_respon>
	<pro_stato>In corso</pro_stato>
	<pro_dtarr>2003-11-19</pro_dtarr>
	<pro_ricpro>N</pro_ricpro>
</dati_procedimento>

ll documento XML del parametro di input xml_richiesta possiede la seguente struttura 
gerarchica :
<wm_attiva_procedimento> ...

La struttura descritta  riconducibile al seguente schema XSD:

<?xml version="1.0" standalone="yes"?>
<xs:schema xmlns="" xmlns:xs="http://www.w3.org/2001/XMLSchema" id="wm_attiva_procedimento">
	<xs:element name="wm_attiva_procedimento">
		<xs:complexType>
			<xs:sequence>
				<xs:element name="dati_procedimento">
					<xs:complexType>
						<xs:choice maxOccurs="unbounded">
							<xs:element name="dati_integrazione" minOccurs="0">
								<xs:complexType>
									<xs:sequence>
										<xs:element name="int_numeropr" type="xs:string"/>
										<xs:element name="int_annopr" type="xs:integer"/>
										<xs:element name="int_datapr" type="xs:dateTime"/>
									</xs:sequence>
								</xs:complexType>
							</xs:element>
							<xs:element name="dati_titolare">
								<xs:complexType>
									<xs:sequence>
										<xs:element name="tit_codfisc" type="xs:string" minOccurs="0"/>
										<xs:element name="tit_tiposog" type="xs:string" minOccurs="0"/>
										<xs:element name="tit_cognome" type="xs:string" minOccurs="0"/>
										<xs:element name="tit_nome" type="xs:string" minOccurs="0"/>
										<xs:element name="tit_codluon" type="xs:string" minOccurs="0"/>
										<xs:element name="tit_desluon" type="xs:string" minOccurs="0"/>
										<xs:element name="tit_codpron" type="xs:string" minOccurs="0"/>
										<xs:element name="tit_dtnas" type="xs:date" minOccurs="0"/>
										<xs:element name="tit_sesso" type="xs:string" minOccurs="0"/>
										<xs:element name="tit_codcomr" type="xs:string" minOccurs="0"/>
										<xs:element name="tit_descomr" type="xs:string" minOccurs="0"/>
										<xs:element name="tit_codpror" type="xs:string" minOccurs="0"/>
										<xs:element name="tit_capr" type="xs:string" minOccurs="0"/>
										<xs:element name="tit_codres" type="xs:string" minOccurs="0"/>
										<xs:element name="tit_desindr" type="xs:string" minOccurs="0"/>
										<xs:element name="tit_numciv" type="xs:int" minOccurs="0"/>
										<xs:element name="tit_desnatg" type="xs:string" minOccurs="0"/>
										<xs:element name="tit_numtel" type="xs:string" minOccurs="0"/>
										<xs:element name="tit_codcit" type="xs:string" minOccurs="0"/>
										<xs:element name="tit_descit" type="xs:string" minOccurs="0"/>
									</xs:sequence>
								</xs:complexType>
							</xs:element>
							<xs:element name="dati_richiedente">
								<xs:complexType>
									<xs:sequence>
										<xs:element name="ric_codfisc" type="xs:string" minOccurs="0"/>
										<xs:element name="ric_tiposog" type="xs:string" minOccurs="0"/>
										<xs:element name="ric_cognome" type="xs:string" minOccurs="0"/>
										<xs:element name="ric_nome" type="xs:string" minOccurs="0"/>
										<xs:element name="ric_codluon" type="xs:string" minOccurs="0"/>
										<xs:element name="ric_desluon" type="xs:string" minOccurs="0"/>
										<xs:element name="ric_codpron" type="xs:string" minOccurs="0"/>
										<xs:element name="ric_dtnas" type="xs:date" minOccurs="0"/>
										<xs:element name="ric_sesso" type="xs:string" minOccurs="0"/>
										<xs:element name="ric_codcomr" type="xs:string" minOccurs="0"/>
										<xs:element name="ric_descomr" type="xs:string" minOccurs="0"/>
										<xs:element name="ric_codpror" type="xs:string" minOccurs="0"/>
										<xs:element name="ric_capr" type="xs:string" minOccurs="0"/>
										<xs:element name="ric_codres" type="xs:string" minOccurs="0"/>
										<xs:element name="ric_desindr" type="xs:string" minOccurs="0"/>
										<xs:element name="ric_numciv" type="xs:int" minOccurs="0"/>
										<xs:element name="ric_desnatg" type="xs:string" minOccurs="0"/>
										<xs:element name="ric_numtel" type="xs:string" minOccurs="0"/>
										<xs:element name="ric_codcit" type="xs:string" minOccurs="0"/>
										<xs:element name="ric_descit" type="xs:string" minOccurs="0"/>
									</xs:sequence>
								</xs:complexType>
							</xs:element>
							<xs:element name="dati_allegati">
								<xs:complexType>
									<xs:sequence>
										<xs:element name="all_blob" type="xs:base64Binary" minOccurs="0"/>
										<xs:element name="all_descri" type="xs:string" minOccurs="0"/>
										<xs:element name="all_tipo" type="xs:string" minOccurs="0"/>
										<xs:element name="all_nomefile" type="xs:string" minOccurs="0"/>
										<xs:element name="all_firma" type="xs:string" minOccurs="0"/>
									</xs:sequence>
								</xs:complexType>
							</xs:element>
						</xs:choice>
					</xs:complexType>
				</xs:element>
			</xs:sequence>
		</xs:complexType>
	</xs:element>
</xs:schema>


Il documento XML che segue rappresenta un esempio coerente con lo schema sopra 
descritto:

<?xml version="1.0" standalone="yes"?>
<wm_attiva_procedimento xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:noNamespaceSchemaLocation="C:\Documents and Settings\VitDe\Desktop\pratiche\wm_attiva_procedimento.xsd">
	<dati_procedimento>
		<dati_titolare>
			<tit_codfisc>NNNMRC65R12H294J</tit_codfisc>
			<tit_tiposog>FI</tit_tiposog>
			<tit_cognome>NANNI</tit_cognome>
			<tit_nome>MARCO</tit_nome>
			<tit_codluon/>
			<tit_desluon>RIMINI</tit_desluon>
			<tit_codpron>RN</tit_codpron>
			<tit_dtnas>1965-02-02</tit_dtnas>
			<tit_sesso>M</tit_sesso>
			<tit_codcomr/>
			<tit_descomr>FORLI'</tit_descomr>
			<tit_codpror>FC</tit_codpror>
			<tit_capr>47100</tit_capr>
			<tit_codres>0</tit_codres>
			<tit_desindr>VIA ARNIER</tit_desindr>
			<tit_numciv>25</tit_numciv>
			<tit_desnatg/>
			<tit_numtel>347</tit_numtel>
			<tit_codcit/>
			<tit_descit>ITALIANA</tit_descit>
		</dati_titolare>
		<dati_allegati>
			<all_blob>MIIMcQYJKoZIhvcNAQcCoIIMYjCCD</all_blob>
			<all_descri>Riepilogo dati Titolare e/o Richiedente</all_descri>
			<all_tipo>7</all_tipo>
			<all_nomefile>docprc0.htm.p7m</all_nomefile>
			<all_firma>S</all_firma>
		</dati_allegati>
	</dati_procedimento>
</wm_attiva_procedimento>

3.4        Web-Method: wm_doc 
 [WebMethod]
string wm_doc (long blo_id)

Argomenti
Wm_doc: stringa contenente documento XML con BLOB del documento richiesto.
blo_id: identificativo univoco del blob da prelevare
Scopo
Recupero del file allegato relativo ad una pratica per una successiva visualizzazione

Messaggio SOAP per linvocazione del servizio.

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

<soap:Envelope 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <wm_doc xmlns="http://localhost/ws_doc/schema">
      <blo_id>long</blo_id>
    </wm_doc>
  </soap:Body>
</soap:Envelope>

Messaggio SOAP di risposta

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

<soap:Envelope 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <wm_docResponse xmlns="http://localhost/ws_doc/schema">
      <wm_docResult>string</wm_docResult>
    </wm_docResponse>
  </soap:Body>
</soap:Envelope> binary large object



Il documento XML contenuto nel campo stringa non possiede alcuna particolare struttura 
gerarchica ma contiene BLOB (Binary Large Object) come valore dellelemento 
<doc_blob>.

La struttura XML descritta in precedenza  riconducibile al seguente schema XSD (XML 
Schema Definition).



<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" 
attributeFormDefault="unqualified">
	<xs:element name="wm_doc">
		<xs:annotation>
			<xs:documentation>Estrazione blob</xs:documentation>
		</xs:annotation>
		<xs:complexType>
			<xs:sequence>
				<xs:element name="doc_blob" type="xs:base64Binary" minOccurs="0">
					<xs:annotation>
						<xs:documentation>Blob</xs:documentation>
					</xs:annotation>
				</xs:element>
			</xs:sequence>
		</xs:complexType>
	</xs:element>
</xs:schema>

Esempio di schema XML congruente con lo schema XSD sopra descritto:

<?xml version="1.0" encoding="utf-8"?>
<wm_doc xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:noNamespaceSchemaLocation="http://www.cedaf.it/schema/Procedimenti//wm_doc.xsd">
	<doc_blob>Tm90ZSA6IERFSkFOIFZJVExBQ0lMIA==</doc_blob>
</wm_doc>

3.5        Web-Method: wm_oneri 
 [WebMethod]
string wm_oneri (long docid)

Argomenti
Wm_oneri: stringa contenente documento XML con gli oneri e le relative rate da 
pagare e/o quelle gi pagate.
docid: identificativo univoco del documento da prelevare
Scopo
Visualizzazione della situazione che riguarda gli oneri e le relative rate da pagare e/o 
quelle gi pagate 

Messaggio SOAP per linvocazione del servizio.

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <wm_oneri xmlns="http://localhost:/aspnet/ws_pratiche/schema">
      <docid>long</docid>
    </wm_oneri>
  </soap:Body>
</soap:Envelope>

Messaggio SOAP di risposta

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <wm_oneriResponse xmlns="http://localhost:/aspnet/ws_pratiche/schema">
      <wm_oneriResult>string</wm_oneriResult>
    </wm_oneriResponse>
  </soap:Body>
</soap:Envelope>


l documento XML wm_oneri (loutput) possiede la seguente struttura gerarchica.
<wm_oneri> root
	<oneri> firstchild
		<lista attributi> ...

La struttura XML descritta in precedenza  riconducibile al seguente schema XSD (XML 
Schema Definition).


<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" 
attributeFormDefault="unqualified">
	<xs:element name="wm_oneri">
		<xs:annotation>
			<xs:documentation>web method wm_oneri</xs:documentation>
		</xs:annotation>
		<xs:complexType>
			<xs:sequence>
				<xs:element name="oneri" minOccurs="0" maxOccurs="unbounded">
					<xs:annotation>
						<xs:documentation>Oneri </xs:documentation>
					</xs:annotation>
					<xs:complexType>
						<xs:sequence>
							<xs:element name="one_docid" type="xs:long" minOccurs="0">
								<xs:annotation>
									<xs:documentation>Id Documento</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="one_ogg" type="xs:string" minOccurs="0">
								<xs:annotation>
									<xs:documentation>Oggetto Documento</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="one_nrata" type="xs:int" minOccurs="0">
								<xs:annotation>
									<xs:documentation>Onere - Numero della rata</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="one_codice" type="xs:string" minOccurs="0">
								<xs:annotation>
									<xs:documentation>Codice Onere</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="one_descr" type="xs:string" minOccurs="0">
								<xs:annotation>
									<xs:documentation>Descrizione Onere</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="one_datascad" type="xs:date" minOccurs="0">
								<xs:annotation>
									<xs:documentation>Data Scadenza</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="one_datapag" type="xs:date" minOccurs="0">
								<xs:annotation>
									<xs:documentation>Data Pagamento</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="one_importo" type="xs:float" minOccurs="0">
								<xs:annotation>
									<xs:documentation>Importo onere espresso in euro</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="one_mora" type="xs:float" minOccurs="0">
								<xs:annotation>
									<xs:documentation>Importo mora  espresso in euro</xs:documentation>
								</xs:annotation>
							</xs:element>
						</xs:sequence>
					</xs:complexType>
				</xs:element>
			</xs:sequence>
		</xs:complexType>
	</xs:element>
</xs:schema>

Esempio di schema XML congruente con lo schema XSD sopra descritto:

<?xml version="1.0" encoding="ISO-8859-1"?>
<wm_oneri xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:noNamespaceSchemaLocation="http://www.cedaf.it/schema/Procedimenti/wm_oneri.xsd">
	<oneri>
		<one_docid>56</one_docid>
		<one_ogg>Domanda di.</one_ogg>
		<one_nrata>1</one_nrata>
		<one_codice>DS</one_codice>
		<one_descr>Diritti di Segreteria</one_descr>
		<one_datascad>2004-09-30</one_datascad>
		<one_datapag>2004-09-12</one_datapag>
		<one_importo>250</one_importo>
		<one_mora>0</one_mora>
	</oneri>
	<oneri>
		<one_docid>56</one_docid>
		<one_ogg>Domanda di.</one_ogg>
		<one_nrata>2</one_nrata>
		<one_codice>DS</one_codice>
		<one_descr>Diritti di Segreteria</one_descr>
		<one_datascad>2004-10-31</one_datascad>
		<one_importo>250</one_importo>
		<one_mora>0</one_mora>
	</oneri>
	<oneri>
		<one_docid>56</one_docid>
		<one_ogg>Domanda di.</one_ogg>
		<one_nrata>3</one_nrata>
		<one_codice>DS</one_codice>
		<one_descr>Diritti di Segreteria</one_descr>
		<one_datascad>2004-12-31</one_datascad>
		<one_importo>250</one_importo>
		<one_mora>0</one_mora>
	</oneri></wm_oneri>

3.6        Web-Method: wm_lista_oneri

[WebMethod]
public string wm_lista_oneri (string codice_fiscale, string filtro)
Argomenti
- Wm_lista_oneri: stringa contenente documento XML che fornisce la lista degli oneri 
legata ad un soggetto
- Codice_fiscale: stringa in ingresso che fornisce il codice fiscale della persona della 
quale si vuole otenere la lista degli oneri.
- Filtro: stringa in base la quale  possibile filtrare la lista degli oneri; T se indicato 
oppure se il filtro viene ignorato, fornisce Tutti gli oneri; P fa visualizzare soltanto gli 
oneri pagati mentre N quelli da pagare.  
Scopo
Visualizzazione della lista degli oneri legati ad un individuo 

Messaggio SOAP per linvocazione del servizio.

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <wm_lista_oneri xmlns="http://localhost:/aspnet/ws_pratiche/schema">
      <codice_fiscale>string</codice_fiscale>
      <filtro>string</filtro>
    </wm_lista_oneri>
  </soap:Body>
</soap:Envelope>
Messaggio SOAP di risposta

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <wm_lista_oneriResponse xmlns="http://localhost:/aspnet/ws_pratiche/schema">
      <wm_lista_oneriResult>string</wm_lista_oneriResult>
    </wm_lista_oneriResponse>
  </soap:Body>
</soap:Envelope>



l documento XML wm_lista_oneri (loutput) possiede la seguente struttura gerarchica.
<wm_lista_oneri> root
	<listaoneri> firstchild
		<lista attributi>
Nodo listaoneri implementa una riga  con la seguente struttura.

La struttura XML descritta in precedenza  riconducibile al seguente schema XSD (XML 
Schema Definition).

<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" 
attributeFormDefault="unqualified">
	<xs:element name="wm_lista_oneri">
		<xs:annotation>
			<xs:documentation>web method wm_oneri</xs:documentation>
		</xs:annotation>
		<xs:complexType>
			<xs:sequence>
				<xs:element name="listaoneri" minOccurs="0" maxOccurs="unbounded">
					<xs:annotation>
						<xs:documentation>Oneri </xs:documentation>
					</xs:annotation>
					<xs:complexType>
						<xs:sequence>
							<xs:element name="lon_docid" type="xs:long" minOccurs="0">
								<xs:annotation>
									<xs:documentation>Id Documento</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="lon_ogg" type="xs:string" minOccurs="0">
								<xs:annotation>
									<xs:documentation>Oggetto Documento</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="lon_nrata" type="xs:int" minOccurs="0">
								<xs:annotation>
									<xs:documentation>Onere - Numero della rata</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="lon_codice" type="xs:string" minOccurs="0">
								<xs:annotation>
									<xs:documentation>Codice Onere</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="lon_descr" type="xs:string" minOccurs="0">
								<xs:annotation>
									<xs:documentation>Descrizione Onere</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="lon_datascad" type="xs:dateTime" minOccurs="0">
								<xs:annotation>
									<xs:documentation>Data Scadenza</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="lon_datapag" type="xs:dateTime" minOccurs="0">
								<xs:annotation>
									<xs:documentation>Data Pagamento</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="lon_importo" type="xs:float" minOccurs="0">
								<xs:annotation>
									<xs:documentation>Importo onere espresso in euro</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="lon_mora" type="xs:float" minOccurs="0">
								<xs:annotation>
									<xs:documentation>Importo mora  espresso in euro</xs:documentation>
								</xs:annotation>
							</xs:element>
						</xs:sequence>
					</xs:complexType>
				</xs:element>
			</xs:sequence>
		</xs:complexType>
	</xs:element>
</xs:schema>

Esempio di schema XML congruente con lo schema XSD sopra descritto:

<?xml version="1.0" encoding="ISO-8859-1"?>
<wm_lista_oneri xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:noNamespaceSchemaLocation="http://www.cedaf.it/schema/Procedimenti/wm_lista_oneri">
	<listaoneri>
		<lon_docid>69331</lon_docid>
		<lon_ogg>Domanda di ..</lon_ogg>
		<lon_nrata>1</lon_nrata>
		<lon_codice>C</lon_codice>
		<lon_descr>Costo di Costruzione</lon_descr>
		<lon_datascad>0000-00-00T00:00:00</lon_datascad>
		<lon_datapag>2004-05-26</lon_datapag>
		<lon_importo>0</lon_importo>
		<lon_mora>0</lon_mora>
	</listaoneri>
	<listaoneri>
		<lon_docid>69331</lon_docid>
		<lon_ogg>Domanda di ..</lon_ogg>
		<lon_nrata>2</lon_nrata>
		<lon_codice>C</lon_codice>
		<lon_descr>Costo di Costruzione</lon_descr>
		<lon_datascad>0000-00-00T00:00:00</lon_datascad>
		<lon_datapag>2004-05-26</lon_datapag>
		<lon_importo>0</lon_importo>
		<lon_mora>0</lon_mora>
	</listaoneri>
	<listaoneri>
		<lon_docid>69331</lon_docid>
		<lon_ogg>Domanda di ..</lon_ogg>
		<lon_nrata>3</lon_nrata>
		<lon_codice>C</lon_codice>
		<lon_descr>Costo di Costruzione</lon_descr>
		<lon_datascad>0000-00-00T00:00:00</lon_datascad>
		<lon_datapag>0000-00-00T00:00:00</lon_datapag>
		<lon_importo>0</lon_importo>
		<lon_mora>0</lon_mora>
	</listaoneri>
	<listaoneri>
		<lon_docid>69331</lon_docid>
		<lon_ogg>Domanda di ..</lon_ogg>
		<lon_nrata>1</lon_nrata>
		<lon_codice>U</lon_codice>
		<lon_descr>Onere Totale Urbanizzazione</lon_descr>
		<lon_datascad>0000-00-00T00:00:00</lon_datascad>
		<lon_datapag>2004-05-26</lon_datapag>
		<lon_importo>0</lon_importo>
		<lon_mora>0</lon_mora>
	</listaoneri>
	<listaoneri>
		<lon_docid>69331</lon_docid>
		<lon_ogg>Domanda di ..</lon_ogg>
		<lon_nrata>2</lon_nrata>
		<lon_codice>U</lon_codice>
		<lon_descr>Onere Totale Urbanizzazione</lon_descr>
		<lon_datascad>0000-00-00T00:00:00</lon_datascad>
		<lon_datapag>0000-00-00T00:00:00</lon_datapag>
		<lon_importo>0</lon_importo>
		<lon_mora>0</lon_mora>
	</listaoneri>
	<listaoneri>
		<lon_docid>69331</lon_docid>
		<lon_ogg>Domanda di ..</lon_ogg>
		<lon_nrata>3</lon_nrata>
		<lon_codice>U</lon_codice>
		<lon_descr>Onere Totale Urbanizzazione</lon_descr>
		<lon_datascad>0000-00-00T00:00:00</lon_datascad>
		<lon_datapag>0000-00-00T00:00:00</lon_datapag>
		<lon_importo>0</lon_importo>
		<lon_mora>0</lon_mora>
	</listaoneri>
	<listaoneri>
		<lon_docid>69331</lon_docid>
		<lon_ogg>Domanda di ..</lon_ogg>
		<lon_nrata>1</lon_nrata>
		<lon_codice>D</lon_codice>
		<lon_descr>Smaltimento rifiuti</lon_descr>
		<lon_datascad>0000-00-00T00:00:00</lon_datascad>
		<lon_datapag>0000-00-00T00:00:00</lon_datapag>
		<lon_importo>0</lon_importo>
		<lon_mora>0</lon_mora>
	</listaoneri>
	<listaoneri>
		<lon_docid>69331</lon_docid>
		<lon_ogg>Domanda di ..</lon_ogg>
		<lon_nrata>1</lon_nrata>
		<lon_codice>M</lon_codice>
		<lon_descr>Monetizzazione</lon_descr>
		<lon_datascad>0000-00-00T00:00:00</lon_datascad>
		<lon_datapag>2004-05-26</lon_datapag>
		<lon_importo>0</lon_importo>
		<lon_mora>0</lon_mora>
	</listaoneri>
	<listaoneri>
		<lon_docid>69331</lon_docid>
		<lon_ogg>Domanda di ..</lon_ogg>
		<lon_nrata>1</lon_nrata>
		<lon_codice>U2</lon_codice>
		<lon_descr>Onere di Urbanizzaz. Sec.</lon_descr>
		<lon_datascad>0000-00-00T00:00:00</lon_datascad>
		<lon_datapag>0000-00-00T00:00:00</lon_datapag>
		<lon_importo>0</lon_importo>
		<lon_mora>0</lon_mora>
	</listaoneri>
	<listaoneri>
		<lon_docid>69331</lon_docid>
		<lon_ogg>Domanda di ..</lon_ogg>
		<lon_nrata>1</lon_nrata>
		<lon_codice>U1</lon_codice>
		<lon_descr>Onere di Urbanizzaz. Prim.</lon_descr>
		<lon_datascad>0000-00-00T00:00:00</lon_datascad>
		<lon_datapag>0000-00-00T00:00:00</lon_datapag>
		<lon_importo>0</lon_importo>
		<lon_mora>0</lon_mora>
	</listaoneri>
	<listaoneri>
		<lon_docid>69332</lon_docid>
		<lon_ogg>Domanda di ..</lon_ogg>
		<lon_nrata>1</lon_nrata>
		<lon_codice>C</lon_codice>
		<lon_descr>Costo di Costruzione</lon_descr>
		<lon_datascad>0000-00-00T00:00:00</lon_datascad>
		<lon_datapag>2004-05-26</lon_datapag>
		<lon_importo>0</lon_importo>
		<lon_mora>0</lon_mora>
	</listaoneri>
	<listaoneri>
		<lon_docid>69332</lon_docid>
		<lon_ogg>Domanda di ..</lon_ogg>
		<lon_nrata>2</lon_nrata>
		<lon_codice>C</lon_codice>
		<lon_descr>Costo di Costruzione</lon_descr>
		<lon_datascad>0000-00-00T00:00:00</lon_datascad>
		<lon_datapag>2004-05-26</lon_datapag>
		<lon_importo>0</lon_importo>
		<lon_mora>0</lon_mora>
	</listaoneri>
	<listaoneri>
		<lon_docid>69332</lon_docid>
		<lon_ogg>Domanda di ..</lon_ogg>
		<lon_nrata>3</lon_nrata>
		<lon_codice>C</lon_codice>
		<lon_descr>Costo di Costruzione</lon_descr>
		<lon_datascad>0000-00-00T00:00:00</lon_datascad>
		<lon_datapag>2004-05-26</lon_datapag>
		<lon_importo>0</lon_importo>
		<lon_mora>0</lon_mora>
	</listaoneri>
	<listaoneri>
		<lon_docid>69332</lon_docid>
		<lon_ogg>Domanda di ..</lon_ogg>
		<lon_nrata>1</lon_nrata>
		<lon_codice>U</lon_codice>
		<lon_descr>Onere Totale Urbanizzazione</lon_descr>
		<lon_datascad>0000-00-00T00:00:00</lon_datascad>
		<lon_datapag>2004-05-26</lon_datapag>
		<lon_importo>0</lon_importo>
		<lon_mora>0</lon_mora>
	</listaoneri>
	<listaoneri>
		<lon_docid>69332</lon_docid>
		<lon_ogg>Domanda di ..</lon_ogg>
		<lon_nrata>2</lon_nrata>
		<lon_codice>U</lon_codice>
		<lon_descr>Onere Totale Urbanizzazione</lon_descr>
		<lon_datascad>0000-00-00T00:00:00</lon_datascad>
		<lon_datapag>0000-00-00T00:00:00</lon_datapag>
		<lon_importo>0</lon_importo>
		<lon_mora>0</lon_mora>
	</listaoneri>
	<listaoneri>
		<lon_docid>69332</lon_docid>
		<lon_ogg>Domanda di ..</lon_ogg>
		<lon_nrata>3</lon_nrata>
		<lon_codice>U</lon_codice>
		<lon_descr>Onere Totale Urbanizzazione</lon_descr>
		<lon_datascad>0000-00-00T00:00:00</lon_datascad>
		<lon_datapag>0000-00-00T00:00:00</lon_datapag>
		<lon_importo>0</lon_importo>
		<lon_mora>0</lon_mora>
	</listaoneri>
	<listaoneri>
		<lon_docid>69332</lon_docid>
		<lon_ogg>Domanda di ..</lon_ogg>
		<lon_nrata>1</lon_nrata>
		<lon_codice>D</lon_codice>
		<lon_descr>Smaltimento rifiuti</lon_descr>
		<lon_datascad>0000-00-00T00:00:00</lon_datascad>
		<lon_datapag>2004-05-26</lon_datapag>
		<lon_importo>0</lon_importo>
		<lon_mora>0</lon_mora>
	</listaoneri>
	<listaoneri>
		<lon_docid>69332</lon_docid>
		<lon_ogg>Domanda di ..</lon_ogg>
		<lon_nrata>1</lon_nrata>
		<lon_codice>M</lon_codice>
		<lon_descr>Monetizzazione</lon_descr>
		<lon_datascad>0000-00-00T00:00:00</lon_datascad>
		<lon_datapag>2004-05-26</lon_datapag>
		<lon_importo>0</lon_importo>
		<lon_mora>0</lon_mora>
	</listaoneri>
	<listaoneri>
		<lon_docid>69332</lon_docid>
		<lon_ogg>Domanda di ..</lon_ogg>
		<lon_nrata>1</lon_nrata>
		<lon_codice>U2</lon_codice>
		<lon_descr>Onere di Urbanizzaz. Sec.</lon_descr>
		<lon_datascad>0000-00-00T00:00:00</lon_datascad>
		<lon_datapag>0000-00-00T00:00:00</lon_datapag>
		<lon_importo>0</lon_importo>
		<lon_mora>0</lon_mora>
	</listaoneri>
	<listaoneri>
		<lon_docid>69332</lon_docid>
		<lon_ogg>Domanda di ..</lon_ogg>
		<lon_nrata>1</lon_nrata>
		<lon_codice>U1</lon_codice>
		<lon_descr>Onere di Urbanizzaz. Prim.</lon_descr>
		<lon_datascad>0000-00-00T00:00:00</lon_datascad>
		<lon_datapag>0000-00-00T00:00:00</lon_datapag>
		<lon_importo>0</lon_importo>
		<lon_mora>0</lon_mora>
	</listaoneri>
	<listaoneri>
		<lon_docid>69333</lon_docid>
		<lon_ogg>Domanda di ..</lon_ogg>
		<lon_nrata>1</lon_nrata>
		<lon_codice>C</lon_codice>
		<lon_descr>Costo di Costruzione</lon_descr>
		<lon_datascad>0000-00-00T00:00:00</lon_datascad>
		<lon_datapag>0000-00-00T00:00:00</lon_datapag>
		<lon_importo>0</lon_importo>
		<lon_mora>0</lon_mora>
	</listaoneri>
</wm_lista_oneri>



3.7        Web-Method: wm_pagato
 [WebMethod]
string wm_pagato (string ls_oneri)

Argomenti
- Wm_pagato: stringa contenente documento XML che fornisce lesito del 
laggiornamento del campo data pagamento
- ls_oneri: stringa in ingresso che fornisce il codice documento, il codice onere, la data 
pagamento e numero rata, necessari per la individuazione del record richiesto. 

La struttura di ls_oneri (Input)  riconducibile al seguente schema XSD (XML Schema 
Definition).

<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSPY v5 rel. 3 U (http://www.xmlspy.com) by RICCI CLAUDIO (CEDAF SRL) -->
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" 
attributeFormDefault="unqualified">
	<xs:element name="wm_pagatoInput">
		<xs:annotation>
			<xs:documentation>Input per il web method wm_pagato</xs:documentation>
		</xs:annotation>
		<xs:complexType>
			<xs:sequence>
				<xs:element name="oneri">
					<xs:annotation>
						<xs:documentation>Oneri</xs:documentation>
					</xs:annotation>
					<xs:complexType>
						<xs:sequence>
							<xs:element name="one_docid" type="xs:long">
								<xs:annotation>
									<xs:documentation>Id Documento</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="one_nrata" type="xs:int">
								<xs:annotation>
									<xs:documentation>Onere - Numero della rata</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="one_codice" type="xs:string">
								<xs:annotation>
									<xs:documentation>Codice Onere</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="one_descr" type="xs:string" minOccurs="0">
								<xs:annotation>
									<xs:documentation>Descrizione Onere</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="one_datascad" type="xs:date" minOccurs="0">
								<xs:annotation>
									<xs:documentation>Data Scadenza</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="one_datapag" type="xs:date">
								<xs:annotation>
									<xs:documentation>Data Pagamento</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="one_importo" type="xs:float" minOccurs="0">
								<xs:annotation>
									<xs:documentation>Importo onere espresso in euro</xs:documentation>
								</xs:annotation>
							</xs:element>
							<xs:element name="one_mora" type="xs:float" minOccurs="0">
								<xs:annotation>
									<xs:documentation>Importo mora  espresso in euro</xs:documentation>
								</xs:annotation>
							</xs:element>
						</xs:sequence>
					</xs:complexType>
				</xs:element>
			</xs:sequence>
		</xs:complexType>
	</xs:element>
</xs:schema>

Esempio di schema XML congruente con lo schema XSD sopra descritto:

<?xml version="1.0" encoding="ISO-8859-1"?>
<wm_oneri xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:noNamespaceSchemaLocation="http://www.cedaf.it/schema/Procedimenti/wm_oneri.xsd">
	<oneri>
		<one_docid>55</one_docid>
		<one_nrata>1</one_nrata>
		<one_codice>D</one_codice>
		<one_descr>On. aggiuntivi smalt. rifiuti</one_descr>
		<one_datascad>2004-06-30</one_datascad>
		<one_datapag>2004-06-11</one_datapag>
		<one_importo>200</one_importo>
		<one_mora>0</one_mora>
	</oneri>
</wm_oneri>

Scopo
Aggiornamento del campo data pagamento 

Messaggio SOAP per linvocazione del servizio.

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <wm_pagato xmlns="http://localhost:/aspnet/ws_pratiche/schema">
      <ls_oneri>string</ls_oneri>
    </wm_pagato>
  </soap:Body>
</soap:Envelope>

Messaggio SOAP di risposta

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xmlns:xsd="http://www.w3.org/2001/XMLSchema" 
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
  <soap:Body>
    <wm_pagatoResponse xmlns="http://localhost:/aspnet/ws_pratiche/schema">
      <wm_pagatoResult>string</wm_pagatoResult>
    </wm_pagatoResponse>
  </soap:Body>
</soap:Envelope>


l documento XML wm_pagato (loutput) possiede la seguente struttura gerarchica.
<wm_pagato> root
	<lista attributi> ...

La struttura XML descritta in precedenza  riconducibile al seguente schema XSD (XML 
Schema Definition).


<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" 
attributeFormDefault="unqualified">
	<xs:element name="wm_pagato">
		<xs:annotation>
			<xs:documentation>web method wm_pagato</xs:documentation>
		</xs:annotation>
		<xs:complexType>
			<xs:sequence>
				<xs:element name="pag_docid" type="xs:long" minOccurs="0">
					<xs:annotation>
						<xs:documentation>Id documento </xs:documentation>
					</xs:annotation>
				</xs:element>
				<xs:element name="pag_nrata" type="xs:int" minOccurs="0">
					<xs:annotation>
						<xs:documentation>Numero di rata da pagare</xs:documentation>
					</xs:annotation>
				</xs:element>
				<xs:element name="pag_onecod" type="xs:string" minOccurs="0">
					<xs:annotation>
						<xs:documentation>Codice onere</xs:documentation>
					</xs:annotation>
				</xs:element>
				<xs:element name="pag_datapag" type="xs:date" minOccurs="0">
					<xs:annotation>
						<xs:documentation>Data del pagamento</xs:documentation>
					</xs:annotation>
				</xs:element>
				<xs:element name="pag_esito" type="xs:string" minOccurs="0">
					<xs:annotation>
						<xs:documentation>Esito</xs:documentation>
					</xs:annotation>
				</xs:element>
			</xs:sequence>
		</xs:complexType>
	</xs:element>
</xs:schema>

Esempio di schema XML congruente con lo schema XSD sopra descritto:

<?xml version="1.0" encoding="ISO-8859-1"?>
<wm_pagato xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:noNamespaceSchemaLocation="http://www.cedaf.it/schema/Procedimenti/wm_pagato.xsd">
	<pag_docid>55</pag_docid>
	<pag_nrata>1</pag_nrata>
	<pag_onecod>D</pag_onecod>
	<pag_datapag>1976-08-20</pag_datapag>
	<pag_esito>Aggiornamento riuscito</pag_esito>
</wm_pagato>


 3.8	Gestione Errori

In caso di errore il documento XML contenuto nel campo stringa possiede la seguente 
struttura gerarchica:

<errore>
(lista attributi)

Il campo codice errore (cod_err) pu assumere i seguenti valori:
	0 = record non trovato
	1 = errore di sistema
	2 = errore applicativo

La struttura XML descritta in precedenza  riconducibile al seguente schema XSD (XML 
Schema Definition).

<?xml version="1.0" encoding="ISO-8859-1"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" 
attributeFormDefault="unqualified">
	<xs:element name="errore">
		<xs:annotation>
			<xs:documentation>Schema per comunicazione errori</xs:documentation>
		</xs:annotation>
		<xs:complexType>
			<xs:sequence>
				<xs:element name="cod_err" type="xs:string">
					<xs:annotation>
						<xs:documentation>Codice errore</xs:documentation>
					</xs:annotation>
				</xs:element>
				<xs:element name="des_err" type="xs:string">
					<xs:annotation>
						<xs:documentation>Descrizione errore generica</xs:documentation>
					</xs:annotation>
				</xs:element>
				<xs:element name="det_err" type="xs:string">
					<xs:annotation>
						<xs:documentation>Descrizione errore dettagliata</xs:documentation>
					</xs:annotation>
				</xs:element>
			</xs:sequence>
		</xs:complexType>
	</xs:element>
</xs:schema>



Esempio di schema XML congruente con lo schema XSD sopra descritto:

<?xml version="1.0" encoding="ISO-8859-1"?>
<errore xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:noNamespaceSchemaLocation="http://www.cedaf.it/schema/errore.xsd">
	<cod_err>1</cod_err>
	<des_err>manca il collegamento</des_err>
	<det_err/>
</errore>




4. Bibliografia
Documenti rilasciati dal Centro Nazionale per lInformatica nella Pubblica
Amministrazione (AIPA-CNIPA):
[AP1] AIPA, "Servizio di cooperazione applicativa basata su eventi", Quaderni 
AIPA Dicembre 1999 

Documenti rilasciati dal W3C:
[W1] D. Box, D. Ehnebuske, G. Kakivaya, A. Layman, N. Mendelsohn, H. F. Nielsen,
S. Thatte, D. Winer, Simple Object Access Protocolo (SOAP) 1.1, W3C, 8 Maggio
2000 
[W2] E. Christensen, F. Curbera, G. Meredith, S. Weerawarena, Web Services
Description Language (WSDL) 1.1, W3C, 15 Marzo 200


