Web Service: service_ConsultaGuiaTratamentoProcessRequest
Target Namespace:
http://xmlns.dmm.spms.pt/201207/ConsultaGuiaTratamento
Port port_ConsultaGuiaTratamentoProcessRequest Port typeSource code
Location:
http://localhost:8080/ode/processes/ConsultaGuiaTratamentoProcessRequest
Protocol:
SOAP
Default style:
document
Transport protocol:
SOAP over HTTP
Operations:
- operation_ConsultaGuiaTratamentoProcessRequestDetailSource code
Operations
- operation_ConsultaGuiaTratamentoProcessRequestOperation type:Request-response. The endpoint receives a message, and sends a correlated message.SOAP action:http://xmlns.dmm.spms.pt/201207/ConsultaGuiaTratamento/initiateInput:message_ConsultaGuiaTratamentoProcessRequest (soap:body, use = literal)Source codeinput type ConsultaGuiaTratamentoProcessRequestOutput:message_ConsultaGuiaTratamentoProcessOutput (soap:body, use = literal)Source coderesult type ConsultaGuiaTratamentoProcessOutput
- output type anyType
Port type port_ConsultaGuiaTratamentoProcessRequestSource code
WSDL source code
<?xml version="1.0"?>
<definitions name="ConsultaGuiaTratamentoRequest" targetNamespace="http://xmlns.dmm.spms.pt/201207/ConsultaGuiaTratamento"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype"
xmlns:tns="http://xmlns.dmm.spms.pt/201207/ConsultaGuiaTratamento"
><!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
TYPE DEFINITION - List of services participating in this BPEL process
The default output of the BPEL designer uses strings as input and
output to the BPEL Process. But you can define or import any XML
Schema type and us them as part of the message types.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<types>
<schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://xmlns.dmm.spms.pt/201207/ConsultaGuiaTratamento"
</types> xmlns="http://www.w3.org/2001/XMLSchema"
><element name="ConsultaGuiaTratamentoProcessOutput">
</schema><complexType></complexType>
</element><!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
MESSAGE TYPE DEFINITION - Definition of the message types used as
part of the port type defintions
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
PORT TYPE DEFINITION - A port type groups a set of operations into
a logical service unit.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<!-- portType implemented by the ConsultaGuiaTratamentoProcess BPEL process -->
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
PARTNER LINK TYPE DEFINITION
the ConsultaGuiaTratamentoProcess partnerLinkType binds the provider and
requester portType into an asynchronous conversation.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<plnk:partnerLinkType name="ptlt_ConsultaGuiaTratamentoProcessRequest"></plnk:partnerLinkType>
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
BINDING DEFINITION - Defines the message format and protocol details
for a web service.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
<!-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SERVICE DEFINITION - A service groups a set of ports into
a service unit.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -->
</definitions>About wsdl-viewer.xsl
This document was generated by libxslt XSLT engine. Based on Uche Ogbuji work.
The engine processed the WSDL in XSLT 1.0 compliant mode.
This page has been generated to AMA by wsdl-viewer.xsl, version
3.1.02