Fuse 6 is no longer supported
As of February 2025, Red Hat Fuse 6 is no longer supported. If you are using Fuse 6, please upgrade to Red Hat build of Apache Camel.이 콘텐츠는 선택한 언어로 제공되지 않습니다.
36.2. CustomerService WSDL Contract
Sample WSDL contract 링크 복사링크가 클립보드에 복사되었습니다!
링크 복사링크가 클립보드에 복사되었습니다!
The WSDL contract used in this demonstration is the
CustomerService
WSDL contract, which is available in the following location:
cxf-webinars-jboss-fuse-6.2.1/src/main/resources/wsdl
cxf-webinars-jboss-fuse-6.2.1/src/main/resources/wsdl
Because the WSDL contract is a fairly verbose format, it is not shown in here in full. The main point you need to be aware of is that the
CustomerSerivice
WSDL contract exposes the following operations:
lookupCustomer
- Given a customer ID, the operation returns the corresponding
Customer
data object. updateCustomer
- Stores the given
Customer
data object against the given customer ID. getCustomerStatus
- Returns the status of the customer with the given customer ID.
Parts of the WSDL contract 링크 복사링크가 클립보드에 복사되었습니다!
링크 복사링크가 클립보드에 복사되었습니다!
A WSDL contract has the following main parts:
Port type 링크 복사링크가 클립보드에 복사되었습니다!
링크 복사링크가 클립보드에 복사되었습니다!
The port type is defined in the WSDL contract by the
wsdl:portType
element. It is analogous to an interface and it defines the operations that can be invoked on the Web service.
For example, the following WSDL fragment shows the
wsdl:portType
definition from the CustomerService
WSDL contract:
WSDL binding 링크 복사링크가 클립보드에 복사되었습니다!
링크 복사링크가 클립보드에 복사되었습니다!
A WSDL binding describes how to encode all of the operations and data types associated with a particular port type. A binding is specific to a particular protocol—for example, SOAP or JMS.
WSDL port 링크 복사링크가 클립보드에 복사되었습니다!
링크 복사링크가 클립보드에 복사되었습니다!
A WSDL port specifies the transport protocol and contains addressing data that enables clients to locate and connect to a remote server endpoint.
For example, the
CustomerService
WSDL contract defines the following WSDL port:
The address specified by the
soap:address
element's location
attribute in the original WSDL contract is typically overridden at run time, however.
The getCustomerStatus operation 링크 복사링크가 클립보드에 복사되었습니다!
링크 복사링크가 클립보드에 복사되었습니다!
Because a WSDL contract is fairly verbose, it can be a bit difficult to see what the parameters of an operation are. Typically, for each operation, you can find data types in the XML schema section that represent the operation request and the operation response. For example, the
getCustomerStatus
operation has its request parameters (IN parameters) encoded by the getCustomerStatus
element and its response parameters (OUT parameters) encoded by the getCustomerStatusResponse
element, as follows:
References 링크 복사링크가 클립보드에 복사되었습니다!
링크 복사링크가 클립보드에 복사되었습니다!
For more details about the format of WSDL contracts and how to create your own WSDL contracts, see Writing WSDL Contracts and the Eclipse JAX-WS Tools Component.