FTP Binding Component Extensibility Elements

The FTP Binding Component is bound to either a service consumer or service provider, and the exposed interfaces are defined by a WSDL document. The FTP Binding Component implements a set of extensibility elements specific to the FTP Binding Component so a service can be defined and bound to a FTP protocol.

The FTP Binding Component supports the following extensibility elements:

1. Address: The connectivity element information such as, FTP URL (host, port, login, password), directory listing style, and user defined heuristics for directory listing parsing.

2. Binding: A marker element indicating a FTP binding. This element does not have attributes.

3. Operation: A marker element indicating a FTP operation. This element does not have attributes.

4. Transfer: Specifies a message transfer from a sender and receiver perspective. For example, to specify a message transfer for a service request, there is a sender and a receiver involved and the WSDL document specifies the following:

   1. The target sender sends to: Represented by the attribute ftp:sendTo (the target receiver receives from is represented by attribute ftp:receiveFrom). The additional operations performed before a message is sent (PUT) to target or after a message is received (GET) from the target are called Pre/Post operations.

   2. messageCorrelate: If enabled, a UUID tagging-based message correlation scheme is used to correlate the request/response of a synchronous service.

5. Message: Specifies a message transfer from a service consumer or service provider perspective. The WSDL document can specify the following:

   1. The message repository represented as the ftp:messageRepository attribute. A base directory where all the working directories for a message transfer are created, such as,

      1. inbox: Used for posting requests (by consumer) and polling request (by provider).

      2. instage: Used for staging requests.

      3. outbox: Used for posting responses (by provider) and polling responses (by consumer).

      4. outstage: Used for staging responses.

   2. messageCorrelate: If enabled, a UUID tagging-based message correlation scheme is used to correlate the request/response of a synchronous service.